IESG Narrative Minutes

Narrative Minutes of the IESG Teleconference on 2008-05-22.

Narrative scribe:    Spencer Dawkins <spencer@wonderhamster.org>

Corrections from:

1 Administrivia

  1. Roll Call 
  2. Bash the Agenda
  3. Approval of the Minutes of the past telechat
  4. Review of Action Items from last Telechat

2 Protocol Actions

2.1 WG submission

2.1.1 - New Items

  1. TCP Friendly Rate Control (TFRC): Protocol Specification (Proposed Standard)
    draft-ietf-dccp-rfc3448bis-06.txt
    Token: Lars Eggert Note: Document shepherd: Gorry Fairhurst (gorry@erg.abdn.ac.uk).
    Balloting
    Ballot Comments:
    1. Russ Housley: Discuss [2008-05-21]: should be summary of the changes since RFC 3448
    2. Tim Polk: Comment [2008-05-22]: I support Russ's discuss on the importance of a change summary.

    Telechat:

  2. Multiple Signatures in S/MIME (Proposed Standard)
    draft-ietf-smime-multisig-05.txt
    Token: Tim Polk
    Balloting
    Ballot Comments:
    1. Jari Arkko: Comment [2008-05-22]: Consider writing this as "If either SignerInfo object is missing, the relaying party ..."
    2. Pasi Eronen: Comment [2008-05-22]: I'd suggest doing some editorial work especially in Section 3, 4.6, 5.
      wouldn't hurt to say how the OIDs have been assigned
    3. Dan Romascanu: Comment [2008-05-19]: Discussion section Table of Contents needs to be removed.

    Telechat:

  3. MPLS Multicast Encapsulations (Proposed Standard)
    draft-ietf-mpls-multicast-encaps-09.txt
    Token: Ross Callon
    Balloting
    Ballot Comments:
    1. Lisa Dusseault: Comment [2008-05-06]: Both codepoints can now carry both types of traffic.
    2. Pasi Eronen: Comment [2008-05-22]: upstream-label and multicast-encaps drafts are very difficult to understand without each other
    3. Russ Housley: Comment [2008-05-06]: Vijay Gurbani concerns have not been addressed.
    4. Dan Romascanu: Discuss [2008-05-21]: incompatible changes on the wire including usage of semantics of Ethernet codepoints values without obsoleting RFC3032 and RFC4023?

    Telechat:

  4. Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK) (Proposed Standard)
    draft-ietf-hokey-emsk-hierarchy-05.txt
    Token: Tim Polk Note: proto shepherd is Charles Clancy
    Balloting
    Ballot Comments:
    1. Jari Arkko: Discuss [2008-05-08]:
      separate default KDF would lead to severe interoperability issues without...
      do not believe it is correct for this document to make statement about the free use of the MSK
      would much rather see a limited number of experimental labels created, and have RFC Required IANA rule for any other usage
      applicability note needs expansion

    Telechat:

  5. Path Computation Element (PCE) Communication Protocol (PCEP) (Proposed Standard)
    draft-ietf-pce-pcep-12.txt
    Token: Ross Callon
    Balloting
    Ballot Comments:
    1. Lars Eggert: Discuss [2008-05-20]: suggestions on improving the keepalive mechanism
      Why is a system port (0-1023) required?
      issues with the continued use of TCP-MD5
      Comment [2008-05-20]: suggested changes to 12 sections
    2. Pasi Eronen: Discuss [2008-05-22]:
      it was concluded that BCP107 applies. This is not reflected in the document.
      There is no mandatory-to-implement security mechanism
      using TCP-MD5 for a *new* protocol would seem to require a particularly strong justification.
      Comment [2008-05-22]: numbering of bits is inconsistent
    3. Russ Housley: Discuss [2008-05-21]: IANA is waiting for the authors to confirm that they have identified the actions correctly, and clarify whether specific values are reserved
    4. Chris Newman: Discuss [2008-05-22]: Please provide a reference that defines the formal language
    5. Tim Polk: Discuss [2008-05-21]: Olafur Godmundson's comment on ietf discuss has not been answered
      Discuss discuss: I would like to understand the migration strategy for introduction of new features
      Comment [2008-05-21]: I support Lars discuss with respect to preference of draft-ietf-tcpm-tcp-auth-opt over TCP MD5.
      text suggestions for 7.4.1, 7.5, 4.2.1
    6. Magnus Westerlund: Discuss [2008-05-22]:
      how to trigger a protocol error condition
      how messages must be processed in relation to each other.
      how to increment SID

    Telechat:

  6. LDP extension for Inter-Area LSP (Proposed Standard)
    draft-ietf-mpls-ldp-interarea-03.txt
    Token: Ross Callon
    Balloting
    Ballot Comments:
    1. Lars Eggert: Comment [2008-05-08]: [empty]
    2. Pasi Eronen: Comment [2008-05-08]: nits From Shawn Emery's SecDir review:
    3. Tim Polk: Comment [2008-05-07]: note by Shawn Emery
    4. Dan Romascanu: Comment [2008-05-21]: suggest that appropriate wording about future work on [need to add new management objects] is added to Section 5.
    5. David Ward: Discuss [2008-05-05]:
      draft doesn't solve the problem it set out to solve
      clear drawback is the change to BGP NH validation
      DISCUSS DISCUSS: recommend we convene a discussion of MPLS savvy folks and work through the possible solutions

    Telechat:

  7. A Backward Recursive PCE-based Computation (BRPC) Procedure To Compute Shortest Constrained Inter-domain Traffic Engineering Label Switched Paths (Proposed Standard)
    draft-ietf-pce-brpc-09.txt
    Token: Ross Callon
    Balloting
    Ballot Comments:
    1. Lars Eggert: Comment [2008-05-20]: Ballot Writeup in the tracker shouldn't contain the PROTO write-up

    Telechat:

2.1.2 Returning Items

  1. none

2.2 Individual Submissions

2.2.1 New Items

  1. Internet Message Format (Draft Standard)
    draft-resnick-2822upd-06.txt
    Token: Lisa Dusseault
    Balloting
    Ballot Comments:
    1. Cullen Jennings: Discuss [2008-05-21]: where is the interop report?

    Telechat:

2.2.2 Returning Items

  1. none

3 Document Actions

3.1 WG Submissions

3.1.1 New Items

  1. IPv6 Unicast Address Assignment Considerations (Informational)
    draft-ietf-v6ops-addcon-07.txt
    Token: Ron Bonica
    Balloting
    Ballot Comments:
    1. Jari Arkko: Discuss [2008-05-22]: two small corrections
      Comment [2008-05-22]: multihoming references don't seem adequate.
    2. Lisa Dusseault: Comment [2008-05-06]: a bunch of nits, I liked the doc itself
    3. Pasi Eronen: Discuss [2008-05-22]: having trouble understanding why Sections 3.1 and 3.3 exist.
      Section 6 should say that using subnet prefixes other than /64 breaks security mechanisms
    4. Russ Housley: Discuss [2008-05-06]: changes were agreed based on SecDir Review. No updated version since that discussion.
    5. Tim Polk: Comment [2008-05-07]: useful suggestions in GenArt Review; all changes proposed appear well founded
    6. Dan Romascanu: Discuss [2008-05-21]: WG summary needs some editing
      Comment [2008-05-21]: 3 wording changes
    7. Mark Townsley: Discuss [2008-05-15]: another possible reason for choosing a subnet prefix...
      Nits

    Telechat:

3.1.2 Returning Items

  1. none

3.2 Individual Submissions via AD

3.2.1 New Items

  1. SAVA Testbed and Experiences to Date (Experimental)
    draft-wu-sava-testbed-experience-06.txt
    Token: Jari Arkko
    Balloting
    Ballot Comments:
    1. Jari Arkko: Discuss [2008-05-22]: to ensure that Pekka Savola's comments are addressed.
    2. Lars Eggert: Comment [2008-05-20]: hoped to see some hard measurement data
    3. Russ Housley: Comment [2008-05-19]: Please remove references from the abstract
      Section 1: s/accomplishedaccurately/accomplished accurately/
      Section 5.2 details needed about key management and the cryptographic algorithm are needed for that work to go forward. Perhaps that is left to a future document.
    4. Dan Romascanu: Comment [2008-05-21]: suggest a change in the title of the document; something like 'A SAVA Testbed and Deployment Experience'

    Telechat:

3.2.2 Returning Items

  1. none

3.3 Independent Submissions via RFC Editor

3.3.1 New Items

  1. none

3.3.2 Returning Items

  1. none

4 Working Group Actions

4.1 WG Creation

4.1.1 Proposed for IETF Review

  1. none

4.1.2 Proposed for Approval

  1. Source Address Validation Improvements (savi)
    Token: Jari

    Telechat:

4.2 WG Rechartering

4.2.1 Under evaluation for IETF Review

  1. EAP Method Update (emu)
    Token: Pasi

    Telechat:

4.2.2 Proposed for Approval

  1. RADIUS EXTensions (radext)
    Token: Dan

    Telechat:

  2. Mobility EXTensions for IPv6 (mext)
    Token: Jari

    Telechat:

5. IAB News We can use

  1. we started to plan the IETF week
    IAB plenary on Wednesday
    we plan to let the architecture discussion from the IAB¨retreat have an impact on IAB agenda.
  2. Suggested topics for plenary: UTC: User Traffic Control
    SIDR: Secure Intra Domain Routing
    P2P: Decentralized Architecture
    PF: (Personal) Firewalls: cost an benefits
    IP: Evolution of IP
  3. review of the IRTF anti-spam research group - Wednesday morning.
  4. Bert Wijnen resigns as liaison to the IETF liaison to the IEEE802.1, we have started the process to appoint a new liaison. We have a candidate ...

6. Management Issues

  1. Request to approve an additional port numbers experts (Michelle Cotton)

    Telechat:

7. Agenda Working Group News

Adjourned


Valid HTML 4.01 Strict