GenART Review Assignment for 29 September 2005



Good approximation of what will be included in the Agenda of next Telechat (2005-09-29).

Updated 2:30:34 EDT, September 23, 2005



2. Protocol Actions

Reviews should focus on these questions: "Is this document a
reasonable basis on which to build the salient part of the Internet
infrastructure? If not, what changes would make it so?"

         

2.1 WG Submissions

         

2.1.1 New Item

     

Area

Date

TSV

Definitions of Managed Objects For iFCP (Proposed Standard) - 1 of 11

draft-ietf-ips-ifcp-mib-06.txt

Note: Last Call ends 9/22 - Last Call comments by Bert as notes to rfc editor (midnight)

Token:

Allison Mankin

Reviewer:

David Black



RTG

BGP Route Reflection - An Alternative to Full Mesh IBGP (Draft Standard) - 2 of 11

draft-ietf-idr-rfc2796bis-01.txt [Open Web Ballot]

Token:

Bill Fenner

Reviewer:

Lakshminath Dondeti



APP

IRIS - An Address Registry (areg) Type for the Internet Registry Information Service (Proposed Standard) - 3 of 11

draft-ietf-crisp-iris-areg-12.txt [Open Web Ballot]

Token:

Ted Hardie

Reviewer:

Harald Alvestrand (already reviewed for LC)



INT

Constrained VPN Route Distribution (Proposed Standard) - 4 of 11

draft-ietf-l3vpn-rt-constrain-02.txt

Token:

Mark Townsley

Reviewer:

John Loughney



INT

Virtual Private LAN Service (Proposed Standard) - 5 of 11

draft-ietf-l2vpn-vpls-bgp-05.txt

Note: This document will go forward simultaneously with draft-ietf-l2vpn-vpls-ldp-07.txt

Token:

Mark Townsley

Reviewer:

Elwyn Davies



INT

Virtual Private LAN Services over MPLS (Proposed Standard) - 6 of 11

draft-ietf-l2vpn-vpls-ldp-07.txt

Note: Taking this forward simultaneously with draft-ietf-l2vpn-vpls-bgp

Token:

Mark Townsley

Reviewer:

Elwyn Davies



TSV

Two-Document ballot: - 7 of 11

Communications Resource Priority for the Session Initiation Protocol (SIP) (Proposed Standard) - 7 of 11

draft-ietf-sip-resource-priority-10.txt

Note: These docs were much reviewed (by Chairs, WG and me) on architecture and details, in WG.
The reason-header update submitted for publication a long time before its companion,
but waited, and then had updates for it.

Extending the Session Initiation Protocol Reason Header for Preemption Events (Proposed Standard)

draft-ietf-sipping-reason-header-for-preemption-04.txt

Note: Last Call comments from the AD given in the SIP meeting: the document must be generic,
not have a implied RSVP coupling.
The document has been waiting for the heavily reviewed resource-priority header doc

Token:

Allison Mankin

Reviewer:

Joel Halpern (reviewed -09 and -02 for LC)



SEC

The Use of TESLA in SRTP (Proposed Standard) - 8 of 11

draft-ietf-msec-srtp-tesla-04.txt [Open Web Ballot]

Token:

Russ Housley

Reviewer:

Elwyn Davies (reviewed -03 for LC)



OPS

Sep 22

Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions (Proposed Standard) - 9 of 11

draft-ietf-bridge-ext-v2-07.txt [Open Web Ballot]

Note: IETF Last Call ends 23 Sept.

Token:

Bert Wijnen

Reviewer:

Harald Alvestrand



APP

IANA Considerations for LDAP (BCP) - 10 of 11

draft-ietf-ldapbis-bcp64-05.txt [Open Web Ballot]

Token:

Ted Hardie

Reviewer:

Joel Halpern (already reviewed for LC)



TSV

RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP (Proposed Standard) - 11 of 11

draft-ietf-rohc-rfc3242bis-01.txt

Note: Last Call ends 9/26 - no IETF comments so far, but encouraged.

Token:

Allison Mankin

Reviewer:

Lakshminath Dondeti



INT


DHCP over InfiniBand


draft-ietf-ipoib-dhcp-over-infiniband-10.txt


Note: this item does not yet appear on official agenda, but has been requested to be added. 

Token:

Margaret Wasserman

Reviewer:

Joel Halpern





2.1.2 Returning Item

     

Area

Date

INT

BGP-MPLS IP VPN extension for IPv6 VPN (Proposed Standard) - 1 of 3

draft-ietf-l3vpn-bgp-ipv6-07.txt [Open Web Ballot]

Token:

Mark Townsley

Reviewer:

Mary Barnes (Spencer reviewed -06 for LC)



INT

Authentication of DHCP Relay Agent Options Using IPsec (Proposed Standard) - 2 of 3

draft-ietf-dhc-relay-agent-ipsec-02.txt [Open Web Ballot]

Note: Document has been updated to address discuss comments from Russ and Bert -- on agenda to see if all issues have been resolved or if any remain.

Token:

Margaret Wasserman

Reviewer:

None.



INT

Node-Specific Client Identifiers for DHCPv4 (Proposed Standard) - 3 of 3

draft-ietf-dhc-3315id-for-v4-05.txt [Open Web Ballot]

Note: On agenda to clear David's discuss and check that IANA issues are resolved.  David, section 7 was added to address your concerns.  If they have not been fully addressed, can you let us know what issues remain?

Token:

Margaret Wasserman

Reviewer:

None.



2.2 Individual Submissions

         

2.2.1 New Item

     

Area

Date

GEN

Internet Code Point Assignments for NSAP Addresses (Proposed Standard) - 1 of 2

draft-gray-rfc1888bis-02.txt

Note: 22-Sep-05:  Please review the -02 version which has been submitted, but which is not yet in the archive.

Token:

Margaret Wasserman

Reviewer:

John Loughney



GEN

Sep 22

BCP101 Update for IPR Trust (BCP) - 2 of 2

draft-carpenter-bcp101-update-01.txt [Open Web Ballot]

Note: IETF Last Call ends today (Sep 22nd)

Token:

Bert Wijnen

Reviewer:

None.



2.2.2 Returning Item
      NONE

3. Document Actions

         

3.1 WG Submissions

Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"

         

3.1.1 New Item

     

Area

Date

TSV

Three-Document ballot: - 1 of 4

Architecture for Reliable Server Pooling (Informational) - 1 of 4

draft-ietf-rserpool-arch-10.txt

Note: PROTO Shepherd: Maureen Stillman

Comparison of Protocols for Reliable Server Pooling (Informational)

draft-ietf-rserpool-comp-10.txt

Note: PROTO Shepherd: Maureen Stillman

Threats Introduced by Rserpool and Requirements for Security in response to Threats (Informational)

draft-ietf-rserpool-threats-05.txt

Note: PROTO Shepherd: Maureen Stillman

Token:

Jon Peterson

Reviewer:

Harald Alvestrand



APP

OPES SMTP Use Cases (Informational) - 2 of 4

draft-ietf-opes-smtp-use-cases-03.txt [Open Web Ballot]

Token:

Ted Hardie

Reviewer:

Spencer Dawkins (already reviewed for LC)



SEC

SSH Public Key File Format (Informational) - 3 of 4

draft-ietf-secsh-publickeyfile-09.txt [Open Web Ballot]

Token:

Sam Hartman

Reviewer:

Joel Halpern



GEN

Sep 18

The IEEE 802/IETF Relationship (Informational) - 4 of 4

draft-iab-ieee-802-rel-01.txt [Open Web Ballot]

Note:   This is a document produced by the IAB
  Document has been reviewed by IAB.
  IAB now sollicits review and comments from IESG.

Token:

Bert Wijnen

Reviewer:

John Loughney







3.1.2 Returning Item
      NONE

3.2 Individual Submissions Via AD

Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"

         

3.2.1 New Item

     

Area

Date

APP

LDAP Bulk Update/Replication Protocol (Informational) - 1 of 4

draft-rharrison-lburp-04.txt [Open Web Ballot]

Token:

Ted Hardie

Reviewer:

Lakshminath Dondeti



RTG

Three-Document ballot: [Open Web Ballot] - 2 of 4

OSPF Link-local Signaling (Experimental) - 2 of 4

draft-nguyen-ospf-lls-05.txt

OSPF Out-of-band LSDB resynchronization (Informational)

draft-nguyen-ospf-oob-resync-05.txt

OSPF Restart Signaling (Informational)

draft-nguyen-ospf-restart-05.txt

Token:

Bill Fenner

Reviewer:

Scott Brim (reviewed for LC)



SEC

Use of IKEv2 in The Fibre Channel Security Association Management Protocol (Informational) - 3 of 4

draft-maino-fcsp-02.txt [Open Web Ballot]

Token:

Russ Housley

Reviewer:

Elwyn Davies



GEN

A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA) (Informational) - 4 of 4

draft-smith-oma-urn-00.txt [Open Web Ballot]

Note: Sent to the URN-NID list on August 25th

Token:

Ted Hardie

Reviewer:

Harald Alvestrand



3.2.2 Returning Item
      NONE

3.3 Individual Submissions Via RFC Editor

The IESG will use RFC 3932 responses: 1) The IESG has not
found any conflict between this document and IETF work; 2) The
IESG thinks that this work is related to IETF work done in WG
<X>, but this does not prevent publishing; 3) The IESG thinks
that publication is harmful to work in WG <X> and recommends
not publishing at this time; 4) The IESG thinks that this
document violates the IETF procedures for <X> and should
therefore not be published without IETF review and IESG
approval; 5) The IESG thinks that this document extends an
IETF protocol in a way that requires IETF review and should
therefore not be published without IETF review and IESG approval.

Other matters may be recorded in comments to be passed on
to the RFC Editor as community review of the document.

         

3.3.1 New Item
      NONE
3.3.2 Returning Item
      NONE