Any submission to the ietf intended by the Contributor for publication as all or part of an ietf internet-Draft or rfc and any statement made within the context of an ietf activity is considered an "ietf contribution"


Download 456 b.
Sana08.08.2017
Hajmi456 b.



Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

  • Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

    • The IETF plenary session. − Any IETF working group or portion thereof.
    • The IESG or any member thereof on behalf of the IESG.
    • The IAB or any member thereof on behalf of the IAB.
    • Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices. − The RFC Editor or the Internet-Drafts function.
  • All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).

  • Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.

  • Please consult RFC 5378 and RFC 3979 for details.

  • A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.

  • A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.



TUESDAY, 1300-1500, Room: Imperial B

  • TUESDAY, 1300-1500, Room: Imperial B

  • 5 min. Administrativia (scribes etc), Agenda Bashing, Chairs

  • 15 min. Review of Existing Charter, Milestones, and Document Status, Chairs

  • Rbridges: Base Protocol Specification

      • draft-ietf-trill-rbridge-protocol-12, Radia Perlman, Donald Eastlake, Silvano Gai, Dinesh Dutt, Anoop Ghanwani
    • 10 min. Implementation Experience: Two kinds of Hello, Radia Perlman
    • 15 min. Changes from -10 to -12, Donald Eastlake
    • 10 min. Frame types, encapsulation, and PPP, Erik Norkmark
    • 10 min. IEEE 802.1 comments on the TRILL protocol specification draft,
    • Don Fedyk
    • 10 min. TRILL Header Options: ECN, VLAN Promotion
      • draft-eastlake-trill-rbridge-options-02.txt, Donald Eastlake, Caitlin Bestler
  • 15 min. Additional TRILL Work/Documents, Donald Eastlake

  • 10 min. TRILL OAM, Anoop Ghanwani

  • 10 min. Charter Update, Chairs



COMPLETED

  • COMPLETED

    • (Earlier milestones related to accepting drafts as working group items not listed.)
    • Start work with routing area WG(s) to undertake TRILL extensions  
    • Submit architecture document to IEEE/IETF expert review
    • Submit problem and applicability statement to IESG for Informational RFC


OVERDUE

  • OVERDUE

    • Submit base protocol specification to IEEE/IETF expert review Dec 2007
    • Submit architecture document to the IESG for publication as an Informational RFC March 2008    
    • Base protocol specification submitted to the IESG for publication as a Proposed Standard RFC March 2008
    • Re-charter or shut down the WG Dec 2008


  • TRILL: Problem and Applicability Statement, draft-ietf-trill-prob-06

    • IETF Last Call complete (version -05)
    • Resolving AD Discusses and Comments
  • The Architecture of an RBridge Solution to TRILL, draft-ietf-trill-rbridge-arch-05

    • Timed out and in the opinion of the chairs should be dropped at this point


  • RBridges: Base Protocol Specification, draft-ietf-trill-rbridge-protocol-12

    • WG Last Call comments substantially resolved
    • IEEE 802.1 WG was asked to comment on the draft regarding its effect on the Ethernet service model
    • Planned to be reviewed by IETF Experts: Bernard Aboba and Dan Romascanu
  • RBridge VLAN Mapping, draft-ietf-trill-rbridge-vlan-mapping-00

    • Ready for WG Last Call?


The Liaison on the following slide was sent to IEEE 802.1 Working Group and Donald Eastlake attended a meeting of the IEEE 802.1 Interworking Task Group in January 2009. An update message was sent to 802.1 when the -10 draft was updated to -11.

  • The Liaison on the following slide was sent to IEEE 802.1 Working Group and Donald Eastlake attended a meeting of the IEEE 802.1 Interworking Task Group in January 2009. An update message was sent to 802.1 when the -10 draft was updated to -11.

  • IEEE 802.1’s response is at: http://ieee802.org/1/files/public/docs2009/liaison-to-trill-wg-0309.pdf



To:  Tony Jeffree, Chair, IEEE 802.1 Working Group

  • To:  Tony Jeffree, Chair, IEEE 802.1 Working Group

  • cc:  Paul Nikolich, Chair, IEEE 802 Paul Congdon, IEEE 802.1 Liaison to the IETF Bernard Aboba, IETF Liaison to IEEE 802 Mark Townsley, IETF Internet Area Co-Director Eric Grey, IETF Liaison to IEEE 802.1

  • Dear Tony, As you know, the IETF TRILL Working Group has been developing a protocol for devices called RBridges (Routing Bridges). We believe that the draft specification of the TRILL protocol (the protocol that is implemented by RBridges) has reached a stage of maturity where, as required by the TRILL WG Charter, it would be appropriate to request IEEE 802.1 to comment on the draft, particularly from the point of view of its effect on the Ethernet Service model. The current version is available at http://www.ietf.org/internet-drafts/draft-ietf-trill-rbridge-protocol-10.txt We look forward to receiving any comments IEEE 802.1 should choose to provide.

  • Sincerely Yours, Donald Eastlake 3rd & Erik Nordmark Co-Chairs, IETF TRILL Working Group



IS-IS Extensions for Layer 2 Systems

  • IS-IS Extensions for Layer 2 Systems

    • draft-ietf-isis-layer2-00.txt, produced from:
  • RBridges: TRILL Header Options

    • draft-eastlake-trill-rbridge-options-02.txt
  • RBridges: Notes

    • draft-eastlake-trill-rbridge-notes-01.txt



Do'stlaringiz bilan baham:


Ma'lumotlar bazasi mualliflik huquqi bilan himoyalangan ©fayllar.org 2017
ma'muriyatiga murojaat qiling