FW: PRELIMINARY Agenda and Package for February 22, 2007 Telechat

Please find below the documents brought for approval at the IESG
telechat on 2/22. Please let me know if there are any issues or concerns
until 2/21 COB the latest.=20

Thanks and Regards,

Dan

         =20
     =20
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-iptel-tgrep-08.txt
    A Telephony Gateway REgistration Protocol (TGREP) (Proposed
Standard)
- 1=20
    of 7=20
    Note: Proto shepherd in Jonathan Rosenberg=20
    Token: Cullen Jennings
  o draft-ietf-pim-bidir-08.txt
    Bi-directional Protocol Independent Multicast (BIDIR-PIM) (Proposed=20
    Standard) - 2 of 7=20
    Token: Bill Fenner
  o draft-ietf-tsvwg-sctp-auth-07.txt
    Authenticated Chunks for Stream Control Transmission Protocol (SCTP)

    (Proposed Standard) - 3 of 7=20
    Token: Magnus Westerlund
  o draft-ietf-l2tpext-failover-11.txt
    Fail Over extensions for L2TP "failover" (Proposed Standard) - 4 of
7

    Token: Mark Townsley
  o draft-ietf-pwe3-wildcard-pw-type-02.txt
    Wildcard Pseudowire Type (Proposed Standard) - 5 of 7=20
    Token: Mark Townsley
  o draft-ietf-lemonade-deployments-05.txt
    Deployment Considerations for lemonade-compliant Mobile Email (BCP)
-
6 of=20
    7=20
    Token: Ted Hardie
  o draft-ietf-smime-cms-mult-sign-03.txt
    Cryptographic Message Syntax (CMS) Multiple Signer Clarification
(Proposed=20
    Standard) - 7 of 7=20
    Token: Sam Hartman

2.1.2 Returning Item
  o draft-ietf-mipshop-cga-cba-03.txt
    Enhanced Route Optimization for Mobile IPv6 (Proposed Standard) - 1
of
1=20
    Token: Mark Townsley


2.2 Individual Submissions
2.2.1 New Item
  o Five-document ballot:  - 1 of 2
     - draft-legg-xed-rxer-07.txt
       Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One

       (ASN.1) (Proposed Standard)=20
     - draft-legg-xed-rxer-ei-04.txt
       Encoding Instructions for the Robust XML Encoding Rules (RXER)
(Proposed=20
       Standard)=20
     - draft-legg-xed-asd-07.txt
       Abstract Syntax Notation X (ASN.X) (Proposed Standard)=20
     - draft-legg-xed-asd-gserei-03.txt
       Abstract Syntax Notation X (ASN.X) Representation of Encoding=20
       Instructions for the Generic String Encoding Rules (GSER)
(Proposed
=20
       Standard)=20
     - draft-legg-xed-asd-xerei-03.txt
       Abstract Syntax Notation X (ASN.X) Representation of Encoding=20
       Instructions for the XML Encoding Rules (XER) (Proposed Standard)

    Token: Ted Hardie
  o draft-heard-rfc4181-update-00.txt
    RFC 4181 Update to Recognize the IETF Trust (BCP) - 2 of 2=20
    Token: Dan Romascanu

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-mip6-dsmip-problem-03.txt
    Problem Statement: Dual Stack Mobility (Informational) - 1 of 1=20
    Note: PROTO shepherd is Basavaraj Patil
<[email protected]>.=20
    NOTE: There are significant RFC Editor notes!=20
    Token: Jari Arkko

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-kalin-geant-urn-namespace-01.txt
    A URN Namespace for GEANT (Informational) - 1 of 3=20
    Note: Sent to URN-NID list for review in November of 2006=20
    Token: Ted Hardie
  o draft-saintandre-xmpp-urn-02.txt
    A Uniform Resource Name (URN) Namespace for Extensions to the
Extensible=20
    Messaging and Presence Protocol (XMPP) (Informational) - 2 of 3=20
    Note: Sent to URN-NID list in November of 2006=20
    Token: Ted Hardie
  o draft-rissen-bbc-urn-00.txt
    A Uniform Resource Name (URN) Formal Namespace for the British
Broadcasting=20
    Corporation (Informational) - 3 of 3=20
    Note: Sent to the URN-NID list in mid January.=20
    Token: Ted Hardie

3.2.2 Returning Item
NONE
3.3 Independent 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.
=20

                   =20
	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
  o draft-nagami-mip6-nemo-multihome-fixed-network-03.txt
    Multi-homing for small scale fixed network Using Mobile IP and NEMO=20
    (Experimental) - 1 of 1=20
    Token: Jari Arkko

3.3.2 Returning Item
NONE
3.3.3 For Action
  o draft-joslin-config-schema-17.txt
    A Configuration Profile Schema for LDAP-based agents (Informational)
-
1 of=20
    1=20
    Note: Proposed for response 2, note 2 of RFC 3932=20
    Token: Ted Hardie



_______________________________________________
OPS-NM mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ops-nm