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

Please review documents on IESG agenda for Jan 6th



AAA Doctors, 

I wish you all a pleasant time during the changing of the year.
Of course I also wish you all the best for 2005!

But if, between now and Jan 6th you can find some time to review
the below documents (specifically for AAA aspects), then I
would be very pleased in the new year.

Thanks,
Bert

--------------
          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the 2005-01-06 IESG Teleconference

This agenda was generated at 2:29:8 EDT, December 31, 2004
                                                                                
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-ccamp-gmpls-g709-08.txt
    Generalized MPLS (GMPLS) Signaling Extensions for G.709 Optical Transport 
    Networks Control (Proposed Standard) - 1 of 5 
    Note: Participant in PROTO Team Pilot:. Workgroup Chair Followup of AD 
    Evaluation Comments. 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-ad-comments-pilot-00.txt 
    Token: Alex Zinin
  o Three-document ballot:  - 2 of 5
     - draft-ietf-ccamp-gmpls-recovery-functional-03.txt
       Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional 
       Specification (Proposed Standard) 
       Note: Target Category is PS, not INFO as the doc says 
     - draft-ietf-ccamp-gmpls-recovery-terminology-05.txt
       Recovery (Protection and Restoration) Terminology for Generalized 
       Multi-Protocol Label Switching (GMPLS) (Informational) 
       Note: Target Category is INFO, not PS as the doc says 
     - draft-ietf-ccamp-gmpls-recovery-analysis-04.txt
       Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based 
       Recovery Mechanisms (including Protection and Restoration) 
       (Informational) 
    Token: Alex Zinin
  o draft-ietf-ccamp-gmpls-overlay-05.txt
    Generalize Multiprotocol Label Switching(GMPLS) User-Network Interface 
    (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support 
    for the Overlay Model (Proposed Standard) - 3 of 5 
    Token: Alex Zinin
  o draft-ietf-ipsec-rfc2401bis-05.txt
    Security Architecture for the Internet Protocol (Proposed Standard) - 4 of 
    5 
    Token: Russ Housley
  o Three-document ballot:  - 5 of 5
     - draft-ietf-ldapbis-dn-15.txt
       LDAP:String Representation of Distinguished Names (Proposed Standard) 
     - draft-ietf-ldapbis-filter-09.txt
       LDAP: String Representation of Search Filters (Proposed Standard) 
     - draft-ietf-ldapbis-models-12.txt
       LDAP: Directory Information Models (Proposed Standard) 
2.1.2 Returning Item
  o draft-ietf-fax-ffpim-08.txt
    Full-mode Fax Profile for Internet Mail: FFPIM (Proposed Standard) - 1 of 6 
    Note: Returning because there aren't enough positive ballots for 
    approval.  All old discusses have been cleared.  NOTE: doc has been 
    updated to -08 from -07 since the document was placed on the agenda. 
    Token: Scott Hollenbeck
  o Four-document ballot:  - 2 of 6
     - draft-ietf-tewg-diff-te-mam-04.txt
       Maximum Allocation Bandwidth Constraints Model for Diff-Serv-aware MPLS 
       Traffic Engineering (Experimental) 
     - draft-ietf-tewg-diff-te-mar-06.txt
       Max Allocation with Reservation Bandwidth Constraint Model for 
       MPLS/DiffServ TE & Performance Comparisons (Experimental) 
     - draft-ietf-tewg-diff-te-proto-08.txt
       Protocol extensions for support of Differentiated-Service-aware MPLS 
       Traffic Engineering (Proposed Standard) 
       Note: Back on Agenda to see if we can get the DISCUSSes cleared.. Thomas
       and Alex ?? 
     - draft-ietf-tewg-diff-te-russian-07.txt
       Russian Dolls Bandwidth Constraints Model for Diff-Serv-aware MPLS 
       Traffic Engineering (Experimental) 
  o draft-ietf-ospf-ospfv3-auth-06.txt
    Authentication/Confidentiality for OSPFv3 (Proposed Standard) - 3 of 6 
    Note: Participant in PROTO Team pilot:. Working Group Chair Followup of 
    DISCUSS Comments. 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-discuss-pilot-01.txt 
    Token: Bill Fenner
  o draft-ietf-ipsec-rfc2402bis-10.txt
    IP Authentication Header (Proposed Standard) - 4 of 6 
    Token: Russ Housley
  o draft-ietf-ipsec-esn-addendum-03.txt
    Extended Sequence Number Addendum to IPsec DOI for ISAKMP (Proposed 
    Standard) - 5 of 6 
    Token: Russ Housley
  o draft-ietf-ipsec-esp-v3-09.txt
    IP Encapsulating Security Payload (ESP) (Proposed Standard) - 6 of 6 
    Token: Russ Housley


2.2 Individual Submissions
2.2.1 New Item
  o draft-huitema-v6ops-teredo-03.txt
    Teredo: Tunneling IPv6 over UDP through NATs (Proposed Standard) - 1 of 1 
    Token: Margaret Wasserman

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 draft-ietf-lemonade-goals-05.txt
    Goals for Internet Messaging to Support Diverse Service Environments 
    (Informational) - 1 of 1 
    Token: Ted Hardie

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
NONE
3.2.2 Returning Item
NONE
3.3 Individual Submissions Via RFC Editor
	Reviews should focus on these questions: "Does this document
	represent an end run around the IETF's working groups
	or its procedures? Does this document present an incompatible
	change to IETF technologies as if it were compatible?" Other
	matters may be sent to the RFC Editor in private review.

3.3.1 New Item
NONE
3.3.2 Returning Item
  o draft-mills-sntp-v4-00.txt
    Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI 
    (Informational) - 1 of 1 
    Note: 2004-11-24: Successful NTP BOF in Washington DC. This document will 
    be. taken over by the WG. Plan was (IIRC) to publish this document. 
    essentially as is as an informational (snapshot) and use the document. as 
    the basis for a Standards Track document on NTP.. 
    Token: Thomas Narten