[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Please review documents on IESG Agenda for September 29, 2005 Tel echat



AAA-doctors,

as always, pls review from a AAA perspective.

I need your comments/remarks (if any) no later than Wed
28 Sept.

Thanks, Bert

-----Original Message-----
                                                                                
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
  o draft-ietf-ips-ifcp-mib-06.txt
    Definitions of Managed Objects For iFCP (Proposed Standard) - 1 of 11 
    Note: Last Call ends 9/22 - Last Call comments by Bert as notes to rfc 
    editor (midnight) 
    Token: Allison Mankin
  o draft-ietf-idr-rfc2796bis-01.txt
    BGP Route Reflection - An Alternative to Full Mesh IBGP (Draft Standard) - 
    2 of 11 
    Token: Bill Fenner
  o draft-ietf-crisp-iris-areg-12.txt
    IRIS - An Address Registry (areg) Type for the Internet Registry 
    Information Service (Proposed Standard) - 3 of 11 
    Token: Ted Hardie
  o draft-ietf-l3vpn-rt-constrain-02.txt
    Constrained VPN Route Distribution (Proposed Standard) - 4 of 11 
    Token: Mark Townsley
  o draft-ietf-l2vpn-vpls-bgp-05.txt
    Virtual Private LAN Service (Proposed Standard) - 5 of 11 
    Note: This document will go forward simultaneously with 
    draft-ietf-l2vpn-vpls-ldp-07.txt 
    Token: Mark Townsley
  o draft-ietf-l2vpn-vpls-ldp-07.txt
    Virtual Private LAN Services over MPLS (Proposed Standard) - 6 of 11 
    Note: Taking this forward simultaneously with draft-ietf-l2vpn-vpls-bgp 
    Token: Mark Townsley
  o Two-document ballot:  - 7 of 11
     - draft-ietf-sipping-reason-header-for-preemption-04.txt
       Extending the Session Initiation Protocol Reason Header for Preemption 
       Events (Proposed Standard) 
       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 
     - draft-ietf-sip-resource-priority-10.txt
       Communications Resource Priority for the Session Initiation Protocol 
       (SIP) (Proposed Standard) 
       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. 
    Token: Allison Mankin
  o draft-ietf-msec-srtp-tesla-04.txt
    The Use of TESLA in SRTP (Proposed Standard) - 8 of 11 
    Token: Russ Housley
  o draft-ietf-bridge-ext-v2-07.txt
    Definitions of Managed Objects for Bridges with Traffic Classes, Multicast 
    Filtering and Virtual LAN Extensions (Proposed Standard) - 9 of 11 
    Note: IETF Last Call ends 23 Sept. 
    Token: Bert Wijnen
  o draft-ietf-ldapbis-bcp64-05.txt
    IANA Considerations for LDAP (BCP) - 10 of 11 
    Token: Ted Hardie
  o draft-ietf-rohc-rfc3242bis-01.txt
    RObust Header Compression (ROHC): A Link-Layer Assisted Profile for 
    IP/UDP/RTP (Proposed Standard) - 11 of 11 
    Note: Last Call ends 9/26 - no IETF comments so far, but encouraged. 
    Token: Allison Mankin

2.1.2 Returning Item
  o draft-ietf-l3vpn-bgp-ipv6-07.txt
    BGP-MPLS IP VPN extension for IPv6 VPN (Proposed Standard) - 1 of 3 
    Token: Mark Townsley
  o draft-ietf-dhc-relay-agent-ipsec-02.txt
    Authentication of DHCP Relay Agent Options Using IPsec (Proposed Standard) 
    - 2 of 3 
    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
  o draft-ietf-dhc-3315id-for-v4-05.txt
    Node-Specific Client Identifiers for DHCPv4 (Proposed Standard) - 3 of 3 
    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


2.2 Individual Submissions
2.2.1 New Item
  o draft-gray-rfc1888bis-02.txt
    Internet Code Point Assignments for NSAP Addresses (Proposed Standard) - 1 
    of 2 
    Note: 22-Sep-05:Aa Please review the -02 version which has been submitted, 
    but which is not yet in the archive. 
    Token: Margaret Wasserman
  o draft-carpenter-bcp101-update-01.txt
    BCP101 Update for IPR Trust (BCP) - 2 of 2 
    Note: IETF Last Call ends today (Sep 22nd) 
    Token: Bert Wijnen

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
  o Three-document ballot:  - 1 of 4
     - draft-ietf-rserpool-arch-10.txt
       Architecture for Reliable Server Pooling (Informational) 
       Note: PROTO Shepherd: Maureen Stillman 
     - draft-ietf-rserpool-comp-10.txt
       Comparison of Protocols for Reliable Server Pooling (Informational) 
       Note: PROTO Shepherd: Maureen Stillman 
     - draft-ietf-rserpool-threats-05.txt
       Threats Introduced by Rserpool and Requirements for Security in response 
       to Threats (Informational) 
       Note: PROTO Shepherd: Maureen Stillman 
    Token: Jon Peterson
  o draft-ietf-opes-smtp-use-cases-03.txt
    OPES SMTP Use Cases (Informational) - 2 of 4 
    Token: Ted Hardie
  o draft-ietf-secsh-publickeyfile-09.txt
    SSH Public Key File Format (Informational) - 3 of 4 
    Token: Sam Hartman
  o draft-iab-ieee-802-rel-01.txt
    The IEEE 802/IETF Relationship (Informational) - 4 of 4 
    Note: Aa This is a document produced by the IAB. Aa Document has been 
    reviewed by IAB.. Aa IAB now sollicits review and comments from IESG. 
    Token: Bert Wijnen

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
  o draft-rharrison-lburp-04.txt
    LDAP Bulk Update/Replication Protocol (Informational) - 1 of 3 
    Token: Ted Hardie
  o draft-maino-fcsp-02.txt
    Use of IKEv2 in The Fibre Channel Security Association Management Protocol 
    (Informational) - 2 of 3 
    Token: Russ Housley
  o draft-smith-oma-urn-00.txt
    A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA) 
    (Informational) - 3 of 3 
    Note: Sent to the URN-NID list on August 25th 
    Token: Ted Hardie

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
  o draft-carroll-dynmobileip-cdma-05.txt
    Verizon Wireless Dynamic Mobile IP Key Update for cdma2000(R) Networks 
    (Informational) - 1 of 1 
    Note: On agenda to clear David's discuss.&nbsp; David, there is a custom 
    IESG note in the tracker that I believe has been agreed by all parties -- 
    if you would like it to say something else, can you suggest changes? 
    Token: Margaret Wasserman