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

AAA-doctor review: Documents on Agenda for IESG August 19, 2004 T elechat

If you can review one or more of the below documents, pls do so.
I am specifically looking for review from a AAA perspective.

Sending comments /issues sooner rathr than later is preferred.
I will be able to handle them as long as I get them befor say 4pm 
Thursday (Europe) or 10am (US Eastern).

Thanks,
Bert 

-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org]
Sent: vrijdag 13 augustus 2004 00:09
To: iesg@ietf.org
Subject: Preliminary Agenda and Package for August 19, 2004 Telechat



          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the August 19, 2004 IESG Teleconference

..
                                                                                
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-ipp-ops-set2-04.txt
    Internet Printing Protocol(IPP): Job and Printer Administrative Operations 
    (Proposed Standard) - 1 of 4 
    Note: This thing has been around so long that several ADs who provided 
    "yes" or "no ob" ballots have fallen off, so it's now short of the required 
    2/3.Aa I need at least one more "recently new" AD to review the document 
    and provide a positive ballot to have it approved. 
    Token: Scott Hollenbeck
  o draft-ietf-smime-cms-seed-01.txt
    Use of the SEED Encryption Algorithm in CMS (Proposed Standard) - 2 of 4 
    Token: Russ Housley
  o draft-ietf-ipsec-esp-ah-algorithms-01.txt
    Cryptographic Algorithm Implementation Requirements For ESP And AH 
    (Proposed Standard) - 3 of 4 
    Token: Russ Housley
  o draft-ietf-geopriv-pidf-lo-02.txt
    A Presence-based GEOPRIV Location Object Format (Proposed Standard) - 4 of 
    4 
    Token: Ted Hardie

2.1.2 Returning Item
  o draft-ietf-aaa-diameter-mobileip-20.txt
    Diameter Mobile IPv4 Application (Proposed Standard) - 1 of 6 
    Note: Waiting for IANA to give OK on IANA considerations section;. Once we 
    receive that, then Thomas can clear his DISCUSS.. So back on 19 aug 
    telechat to force that decision. 
    Token: Bert Wijnen
  o draft-ietf-sigtran-m2pa-12.txt
    Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer 
    Adaptation Layer (M2PA) (Proposed Standard) - 2 of 6 
    Note: Returning item to clear discuss 
    Token: Jon Peterson
  o draft-ietf-rmonmib-tpm-mib-14.txt
    Transport Performance Metrics MIB (Proposed Standard) - 3 of 6 
    Token: Bert Wijnen
  o Four-document ballot:  - 4 of 6
     - draft-ietf-tewg-diff-te-mam-03.txt
       Maximum Allocation Bandwidth Constraints Model for Diff-Serv-aware MPLS 
       Traffic Engineering (Experimental) 
     - draft-ietf-tewg-diff-te-mar-04.txt
       Max Allocation with Reservation Bandwidth Constraint Model for 
       MPLS/DiffServ TE & Performance Comparisons (Experimental) 
     - draft-ietf-tewg-diff-te-proto-07.txt
       Protocol extensions for support of Differentiated-Service-aware MPLS 
       Traffic Engineering (Proposed Standard) 
       Note: Back on Agenda as a forcing tool to make sure we have ALL DISCUSS 
       comments collected before I go back to authors/wg 
     - draft-ietf-tewg-diff-te-russian-06.txt
       Russian Dolls Bandwidth Constraints Model for Diff-Serv-aware MPLS 
       Traffic Engineering (Experimental) 
    Token: Bert Wijnen
  o draft-ietf-tewg-mib-08.txt
    A Traffic Engineering MIB (Proposed Standard) - 5 of 6 
    Note: Back on agenda to ensure we get Haralds and Allisons issues 
    resolved.. . 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: Bert Wijnen
  o draft-ietf-dhc-subscriber-id-06.txt
    DHCP Subscriber ID Suboption for the DHCP Relay Agent Option (Proposed 
    Standard) - 6 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: Margaret Wasserman


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE
2.2.3 For Action
  o draft-sterman-aaa-sip-03.txt
    RADIUS Extension for Digest Authentication (Standard) - 1 of 1 
    Token: David Kessens

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-fax-gateway-options-07.txt
    Guideline of optional services for Internet FAX Gateway (Informational) - 1 
    of 6 
    Token: Scott Hollenbeck
  o draft-ietf-msec-tesla-intro-02.txt
    TESLA: Multicast Source Authentication Transform Introduction 
    (Informational) - 2 of 6 
    Token: Russ Housley
  o draft-ietf-nsis-signalling-analysis-04.txt
    Analysis of Existing Quality of Service Signaling Protocols (Informational) 
    - 3 of 6 
    Token: Allison Mankin
  o draft-ietf-tewg-interas-mpls-te-req-08.txt
    MPLS Inter-AS Traffic Engineering requirements (Informational) - 4 of 6 
    Note: NOTE WELL: revision 08 should arrive on August 12.. That is the one 
    to be reviewed/approved.. . 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: Bert Wijnen
  o draft-ietf-v6ops-ent-scenarios-05.txt
    IPv6 Enterprise Network Scenarios (Informational) - 5 of 6 
    Token: David Kessens
  o draft-ietf-capwap-problem-statement-01.txt
    CAPWAP Problem Statement (Informational) - 6 of 6 
    Token: Bert Wijnen

3.1.2 Returning Item
  o draft-ietf-ipv6-node-requirements-10.txt
    IPv6 Node Requirements (Informational) - 1 of 1 
    Note: On the agenda for Russ to check (and hopefully clear) the final 
    discuss. 
    Token: Margaret Wasserman


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-dcsgroup-sipping-arch-01.txt
    Architectural Considerations for Providing Carrier Class Telephony Services 
    Utilizing Session Initiation Protocol SIP-based Distributed Call Control 
    Mechanisms (Informational) - 1 of 1 
    Note: Will propose an IESG note modelled like the RFC Editor disclaimer, 
    though it's not an RFC Ed document...even though the SIP folks in times 
    past reviewed it, it differs from the end-to-end design of SIP.Aa 
    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-motonori-dualstack-smtp-requirement-01.txt
    SMTP Operational Experience in Mixed IPv4/v6 Environments (Informational) - 
    1 of 1 
    Token: Bert Wijnen

3.3.2 Returning Item
NONE


Thanks,
Bert