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

Please review documents on IESG Agenda for March 2, 2006 Telechat

AAA_doctors, as always, pls review from an AAA point of view.

Specifically take a look at
   draft-ietf-aaa-diameter-sip-app-11.txt
It makes assignments in the AAA prameters registry.

I need your comments no later than Wed Mar 1st.

Thanks in advance,
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-auth-mib-07.txt
    Definitions of Managed Objects for User Identity Authorization (Proposed 
    Standard) - 1 of 16 
    Note: PROTO Shepherd black_david@emc.com 
    Token: Allison Mankin
  o draft-ietf-ips-iscsi-mib-11.txt
    Definitions of Managed Objects for iSCSI (Proposed Standard) - 2 of 16 
    Note: PROTO Shepherd black_david@emc.com 
    Token: Allison Mankin
  o draft-ietf-ipcdn-docs-rfmibv2-14.txt
    Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 
    compliant RF interfaces (Proposed Standard) - 3 of 16 
    Token: Bert Wijnen
  o draft-ietf-ccamp-rsvp-node-id-based-hello-02.txt
    Node ID based RSVP Hello: A Clarification Statement (Proposed Standard) - 4 
    of 16 
    Token: Alex Zinin
  o draft-ietf-l2tpext-l2vpn-06.txt
    L2VPN Extensions for L2TP (Proposed Standard) - 5 of 16 
    Token: Mark Townsley
  o draft-ietf-netconf-beep-08.txt
    Using the NETCONF Protocol over Blocks Extensible Exchange Protocol (BEEP) 
    (Proposed Standard) - 6 of 16 
    Token: Bert Wijnen
  o Two-document ballot:  - 7 of 16
     - draft-ietf-netconf-ssh-05.txt
       Using the NETCONF Configuration Protocol over Secure Shell (SSH) 
       (Proposed Standard) 
     - draft-ietf-netconf-prot-11.txt
       NETCONF Configuration Protocol (Proposed Standard) 
    Token: Bert Wijnen
  o draft-ietf-netconf-soap-07.txt
    Using the Network Configuration Protocol (NETCONF) Over the Simple Object 
    Access Protocol (SOAP) (Proposed Standard) - 8 of 16 
    Token: Bert Wijnen
  o draft-ietf-aaa-diameter-sip-app-11.txt
    Diameter Session Initiation Protocol (SIP) Application (Proposed Standard) 
    - 9 of 16 
    Token: Bert Wijnen
  o draft-ietf-dhc-server-override-03.txt
    DHCP Server Identifier Override Suboption (Proposed Standard) - 10 of 16 
    Token: Margaret Wasserman
  o draft-ietf-pwe3-fragmentation-10.txt
    PWE3 Fragmentation and Reassembly (Proposed Standard) - 11 of 16 
    Token: Margaret Wasserman
  o draft-ietf-ipoib-connected-mode-02.txt
    IP over InfiniBand: Connected Mode (Proposed Standard) - 12 of 16 
    Token: Margaret Wasserman
  o draft-ietf-geopriv-location-types-registry-04.txt
    Location Types Registry (Proposed Standard) - 13 of 16 
    Token: Ted Hardie
  o draft-ietf-dnsext-ds-sha256-05.txt
    Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs) 
    (Proposed Standard) - 14 of 16 
    Token: Margaret Wasserman
  o draft-ietf-sip-refer-feature-param-01.txt
    Conveying Feature Tags with Session Initiation Protocol REFER Method 
    (Proposed Standard) - 15 of 16 
    Token: Allison Mankin
  o draft-ietf-sipping-uri-services-05.txt
    Framework and Security Considerations for Session Initiation Protocol (SIP) 
    Uniform Resource Identifier (URI)-List Services (Proposed Standard) - 16 of
 
    16 
    Token: Allison Mankin

2.1.2 Returning Item
  o draft-ietf-imapext-condstore-09.txt
    IMAP Extension for Conditional STORE operation (Proposed Standard) - 1 of 2 
    Note: Document shepherd is Lisa Dusseault <lisa@osafoundation.org> 
    Token: Scott Hollenbeck
  o draft-ietf-sip-target-dialog-03.txt
    Request Authorization through Dialog Identification in the Session 
    Initiation Protocol (SIP) (Proposed Standard) - 2 of 2 
    Token: Allison Mankin


2.2 Individual Submissions
2.2.1 New Item
  o draft-salowey-tls-ticket-07.txt
    Transport Layer Security Session Resumption without Server-Side State 
    (Proposed Standard) - 1 of 1 
    Token: Russ Housley

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-ipngwg-icmp-name-lookups-15.txt
    IPv6 Node Information Queries (Experimental) - 1 of 5 
    Note: The PROTO Shepherd is Bob Hinden <hinden@nokia.com>. 
    Token: Margaret Wasserman
  o draft-ietf-idwg-idmef-xml-15.txt
    The Intrusion Detection Message Exchange Format (Experimental) - 2 of 5 
    Note: Returning for publication as an experimental RFC rather than a. 
    proposed standard.  When I talked to the IESG about this the plan was. 
    to completely remove the schema.  The authors really want appendix c. 
    to stay as non-normative; if the IESG cannot accept this then we can. use 
    an rfc editor note. 
    Token: Sam Hartman
  o draft-ietf-tsvwg-diffserv-service-classes-02.txt
    Configuration Guidelines for DiffServ Service Classes (Informational) - 3 
    of 5 
    Note: PROTO shepherd: James Polk <jmpolk@cisco.com>. waiting for 
    writeup 
    Token: Allison Mankin
  o draft-ietf-mip6-bootstrap-ps-04.txt
    Problem Statement for bootstrapping Mobile IPv6 (Informational) - 4 of 5 
    Token: Margaret Wasserman
  o draft-ietf-ediint-as3-04.txt
    FTP Transport for Secure Peer-to-Peer Business Data Interchange over the 
    Internet (Informational) - 5 of 5 
    Note: There has been almost no public discussion of this document within 
    whatever remains of the EDIINT working group.  However, there do appear to 
    be implementations and there thus appears to be value in publishing the 
    document as an Informational RFC.  Significant comments that can not be 
    addressed with an RFC Editor note might not be resolvable. 
    Token: Scott Hollenbeck

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-edwards-mime-mxf-02.txt
    Media Type Registration for SMPTE Material Exchange Format (MXF) 
    (Informational) - 1 of 1 
    Token: Scott Hollenbeck

3.2.2 Returning Item
NONE
3.2.3 For Action
  o draft-hoschka-smil-media-type-12.txt
    The application/smil and application/smil+xml Media Types (Informational) - 
    1 of 1 
    Note: Back on ballot to confirm the IESG is okay with a late change related 
    to SMIL versions.  The substantive change is that SMIL is now being 
    registered as OBSOLETE 
    Token: Ted Hardie
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