[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Pls review documents on IESG agenda
AAA doctors,
As always, pls review the documents on the IESG agenda for
Dec 2nd 2004. Best if you can do so asap, but in any event,
pls send me any concerns/comments you may have no later than
Thursday Dec 2nd 6am US Eastern.
Documents that may need specific attention from AA docutors:
draft-arkko-pppext-eap-aka-13.txt (Informational)
draft-haverinen-pppext-eap-sim-14.txt (Informational)
But of course I'd welcome review of all other docs (specifically
from a AAA perspective) as well.
Thanks,
Bert
--------------
INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the 2004-12-02 IESG Teleconference
This agenda was generated at 18:20:42 EDT, November 25, 2004
.. snip ..
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-l3vpn-ospf-2547-02.txt
OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP VPNs (Proposed
Standard) - 1 of 4
Note: 2004-11-24: Ready for full IESG review. Also, depends on.
draft-ietf-idr-bgp-ext-communities-07.txt to set up IANA registry that. is
populated by this document (see comment from IANA in log)..
Token: Thomas Narten
o draft-ietf-magma-mrdisc-03.txt
Multicast Router Discovery (Proposed Standard) - 2 of 4
Token: Margaret Wasserman
o Two-document ballot: - 3 of 4
- draft-iab-liaison-mgt-02.txt
IAB Processes for management of liaison relationships (BCP)
- draft-baker-liaison-statements-02.txt
Procedure for Handling Liaison Statements Between Standards Bodies (BCP)
Note: See also draft-iab-liaison-mgt
- draft-baker-liaison-statements-02.txt2
Procedure for Handling Liaison Statements Between Standards Bodies (BCP)
Token: Harald Alvestrand
o draft-ietf-avt-rfc2793bis-09.txt
RTP Payload for Text Conversation (Proposed Standard) - 4 of 4
Note: text/red is in revision to be text payload types only. RFC Editor
Note will change IANA Considerations to note text/t140 is an update, not
new
Token: Allison Mankin
2.1.2 Returning Item
o Eight-document ballot: - 1 of 1
- draft-ietf-idr-bgp-implementation-02.txt
BGP 4 Implementation Report (Informational)
- draft-ietf-idr-bgp4-26.txt
A Border Gateway Protocol 4 (BGP-4) (Draft Standard)
Note: Back on the agenda to resolve remaining DISCUSS'es
- draft-ietf-idr-bgp4-mib-15.txt
Definitions of Managed Objects for the Fourth Version of Border Gateway
Protocol (BGP-4) (Proposed Standard)
- draft-ietf-idr-bgp-vuln-01.txt
BGP Security Vulnerabilities Analysis (Informational)
- draft-ietf-idr-bgp-analysis-06.txt
BGP-4 Protocol Analysis (Informational)
- draft-ietf-idr-bgp4-experience-protocol-05.txt
Experience with the BGP-4 Protocol (Informational)
- draft-ietf-idr-bgp-mibagent-survey-02.txt
BGP MIB V1 implementation survey (Informational)
- draft-iesg-tcpmd5app-01.txt
Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC
2385) and the BGP-4 Specification (Informational)
- draft-ietf-idr-bgp-implementation-02.txt2
BGP 4 Implementation Report (Informational)
- draft-ietf-idr-bgp4-mib-15.txt2
Definitions of Managed Objects for the Fourth Version of Border Gateway
Protocol (BGP-4) (Proposed Standard)
- draft-ietf-idr-bgp-vuln-01.txt2
BGP Security Vulnerabilities Analysis (Informational)
- draft-ietf-idr-bgp-analysis-06.txt2
BGP-4 Protocol Analysis (Informational)
- draft-ietf-idr-bgp4-experience-protocol-05.txt2
Experience with the BGP-4 Protocol (Informational)
- draft-ietf-idr-bgp-mibagent-survey-02.txt2
BGP MIB V1 implementation survey (Informational)
- draft-iesg-tcpmd5app-01.txt2
Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC
2385) and the BGP-4 Specification (Informational)
Token: Alex Zinin
2.2 Individual Submissions
2.2.1 New Item
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
o draft-ietf-dna-goals-03.txt
Detecting Network Attachment in IPv6 Goals (Informational) - 1 of 3
Token: Margaret Wasserman
o draft-ietf-multi6-multihoming-threats-02.txt
Threats relating to IPv6 multihoming solutions (Informational) - 2 of 3
Token: David Kessens
o draft-ietf-mboned-ipv6-multicast-issues-01.txt
IPv6 Multicast Deployment Issues (Informational) - 3 of 3
Token: David Kessens
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-arkko-pppext-eap-aka-13.txt
Extensible Authentication Protocol Method for 3rd Generation Authentication
and Key Agreement (EAP-AKA) (Informational) - 1 of 4
Note: 2004-11-23: Ready for full IESG review (when -14 appears). Note:.
needed by 3GPP; document has been reviewed by EAP WG for conformance. with
EAP, but security properties have not (and will not) be. reviewed. Document
has been submitted a independent submission to RFC. Editor, but 3GPP (via
liaison discussions) has requested that the. document be reviewed by IETF
for conformance with EAP..
Token: Thomas Narten
o draft-haverinen-pppext-eap-sim-14.txt
Extensible Authentication Protocol Method for GSM Subscriber Identity
Modules (EAP-SIM) (Informational) - 2 of 4
Note: 2004-11-23: Ready for full IESG review (when -15 appears). Note:.
needed by 3GPP; document has been reviewed by EAP WG for conformance. with
EAP, but security properties have not (and will not) be. reviewed. Document
has been submitted a independent submission to RFC. Editor, but 3GPP (via
liaison discussions) has requested that the. document be reviewed by IETF
for conformance with EAP..
Token: Thomas Narten
o draft-vandesompel-info-uri-02.txt
The 'info' URI Scheme for Information Assets with Identifiers in Public
Namespaces (Informational) - 3 of 4
Token: Ted Hardie
o draft-sangug-uci-urn-00.txt
Using Universal Content Identifier as Uniform Resource Names
(Informational) - 4 of 4
Token: Ted Hardie
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
NONE