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

Pls review Agenda and Package for July 22, 2004 IESG Telechat



AAA-Doctors,

The OPS ADs have a number of places (like MIB doctors and OPS Directorate)
where they ask for help in reviewing documents that are on IESG agenda.

I am think that maybe this group of AAA-Doctors may also be interested
and willing to help. As you probably know, the IESG has bi-weekly 
teleconferences (Telechat we call them) where we discuss and potentially
do approve documents to be published. The Friday before such a telechat we 
get a draft agenda with the documents to be discussed. So if you think
that review by AAA-doctors is a good idea, then pls feel free to send 
me your comments concenrns.

The process:
- I send the docs on agenda to this list on Friday.
- Any AAA-doctor can review these docs. I prefer that this group looks
  specifically at AAA (diameter and radius) aspects in the documents,
  but if you see other major issues, then pls report them.
- I prefer the comments to be in the form that I can make them public,
  but I will honor request for anonymity.
- The idea is that certainly we detect major issues. Minor comments
  and nits can be reported as well, but those will not be used to
  "block" documents. 
- I need such comments back as soon as possible, but in order to feed
  them into the IESG meeting I need them no later than Thursday 4pm
  European (10am US Eastern).

Happy reviewing and Thanks,
Bert 

------------
2.1 WG Submissions
2.1.1 New Item
  o Eight-document ballot:  - 1 of 4
     - draft-ietf-idr-bgp-implementation-01.txt
       BGP 4 Implementation Report (Informational) 
     - draft-ietf-idr-bgp4-24.txt
       A Border Gateway Protocol 4 (BGP-4) (Draft Standard) 
     - draft-ietf-idr-bgp4-mib-14.txt
       Definitions of Managed Objects for the Fourth Version of Border Gateway 
       Protocol (BGP-4) (Proposed Standard) 
     - draft-ietf-idr-bgp-vuln-00.txt
       BGP Security Vulnerabilities Analysis (Informational) 
     - draft-ietf-idr-bgp-analysis-05.txt
       BGP-4 Protocol Analysis (Informational) 
     - draft-ietf-idr-bgp4-experience-protocol-04.txt
       Experience with the BGP-4 Protocol (Informational) 
     - draft-ietf-idr-bgp-mibagent-survey-01.txt
       BGP MIB V1 implementation survey (Informational) 
     - draft-iesg-tcpmd5app-00.txt
       Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 
       2385) and the BGP-4 Specification (Informational) 
    Token: Alex Zinin
  o draft-ietf-opes-http-02.txt
    HTTP adaptation with OPES (Proposed Standard) - 2 of 4 
    Token: Ted Hardie
  o draft-ietf-mmusic-anat-01.txt
    The Alternative Network Address Types Semantics for the Session Description 
    Protocol Grouping Framework (Proposed Standard) - 3 of 4 
    Token: Jon Peterson
  o draft-ietf-sip-anat-usage-00.txt
    Usage of the Session Description Protocol (SDP) Alternative Network Address 
    Types (ANAT) Semantics in the Session Initiation Protocol (SIP) (Proposed 
    Standard) - 4 of 4 
    Note: RFC Editor Note: ANAT to be expanded in Abstract and Intro 
    Token: Allison Mankin

2.1.2 Returning Item
  o draft-ietf-pkix-pi-10.txt
    Internet X.509 Public Key Infrastructure Permanent Identifier (Proposed 
    Standard) - 1 of 3 
    Note: The draft includes significant revisions.  On the agenda to see 
    if the revisions resolve the discuss positions.  Also, given the 
    significant changes, all of the ADs may want to take a fresh look. 
    Token: Russ Housley
  o Two-document ballot:  - 2 of 3
     - draft-ietf-sipping-early-media-02.txt
       Early Media and Ringing Tone Generation in the Session Initiation 
       Protocol (SIP) (Informational) 
     - draft-ietf-sipping-early-disposition-03.txt
       The Early Session Disposition Type for the Session Initiation Protocol 
       (SIP) (Proposed Standard) 
       Note: For re-review by Discussants please. 
    Token: Allison Mankin
  o Three-document ballot:  - 3 of 3
     - draft-ietf-crisp-iris-core-07.txt
       IRIS - The Internet Registry Information Service (IRIS) Core Protocol 
       (Proposed Standard) 
       Note: Returning to resolve outstanding DISCUSS; please be sure to review 
       the -07 versions. 
     - draft-ietf-crisp-iris-dreg-07.txt
       IRIS - A Domain Registry (dreg) Type for the Internet Registry 
       Information Service (Proposed Standard) 
     - draft-ietf-crisp-iris-beep-07.txt
       IRIS - Using the Internet Registry Information Service (IRIS) over the 
       Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard) 
       Note: Needs to add a normative reference to draft-daigle-snaptr-00.txt, 
       which sets up the registry populated here. 
    Token: Ted Hardie


2.2 Individual Submissions
2.2.1 New Item
  o draft-wasserman-rfc2418-ml-update-01.txt
    Update to RFC 2418 Regarding the Management of IETF Mailing Lists (BCP) - 1 
    of 2 
    Token: Harald Alvestrand
  o draft-hansen-lemonade-msgctxt-videomsg-01.txt
    Video Message Message Context (Proposed Standard) - 2 of 2 
    Token: Ted Hardie

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-msec-gkmarch-08.txt
    MSEC Group Key Management Architecture (Informational) - 1 of 2 
    Note: Blue Team. 
    Token: Russ Housley
  o draft-ietf-v6ops-renumbering-procedure-01.txt
    Procedures for Renumbering an IPv6 Network without a Flag Day 
    (Informational) - 2 of 2 
    Note: Note: red team 
    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-torvinen-http-digest-aka-v2-01.txt
    Hypertext Transfer Protocol (HTTP) Digest Authentication Using 
    Authentication and Key Agreement (AKA) Version-2 (Informational) - 1 of 1 
    Token: Allison Mankin

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
  o draft-richardson-ipsec-opportunistic-15.txt
    Opportunistic Encryption using The Internet Key Exchange (IKE) 
    (Informational) - 1 of 1 
    Token: Steve Bellovin

3.3.2 Returning Item
NONE