The design team has updated this document based on comments we received
in the meetings and hallways in the Dallas.

I think the chairs are planning to ask for WG adoption, so it would be
good for folks to take a look at the draft.

The change log section summarizes the changes:
   The changes from draft-rtg-dt-encap-01 based on feedback at the
   Dallas IETF meeting:
   o  Setting the context that not all common issues might apply to all
      encapsulations, but that they should all be understood before
      being dismissed.
   o  Clarified that IPv6 flow label is useful for entropy in
      combination with a UDP source port.
   o  Editorially added a "summary" set of bullets to most sections.
   o  Editorial clarifications in the next protocol section to more
      clearly state the three areas.
   o  Folded the two next protocol sections into one.
   o  Mention the MPLS first nibble issue in the next protocol section.
   o  Mention that viewing the next protocol as an index to a table with
      processing instructions can provide additional flexibility in the
      protocol evolution.
   o  For the OAM "don't forward to end stations" added that defining a
      bit seems better than using a special next-protocol value.
   o  Added mention of DTLS in addition to IPsec for security.
   o  Added some mention of IPv6 hob-by-hop options of other headers
      than potentially can be copied from inner to outer header.
   o  Added text on architectural considerations when it might make
      sense to define an additional header/protocol as opposed to using
      the extensibility mechanism in the existing encapsulation
      protocol.
   o  Clarified the "unconstrained TLVs" in the hardware friendly
      section.
   o  Clarified the text around checksum verification and full vs.
      header checksums.
   o  Added wording that the considerations might apply for encaps
      outside of the routing area.
   o  Added references to draft-ietf-pwe3-congcons,
      draft-ietf-tsvwg-rfc5405bis, RFC2473, and RFC7325
   o  Removed reference to RFC3948.
   o  Updated the acknowledgements section.
   o  Added this change log section.

   Erik (for the design team)



-------- Forwarded Message --------
Subject:        New Version Notification for draft-rtg-dt-encap-02.txt
Date:   Thu, 21 May 2015 19:03:07 -0700
From:   [email protected]
To:     Jon Hudson <[email protected]>, Tom Herbert
<[email protected]>, Lawrence Kreeger <[email protected]>, Patricia
Thaler <[email protected]>, Patricia Thaler <[email protected]>,
Jon Hudson <[email protected]>, Albert Tian
<[email protected]>, Jesse Gross <[email protected]>, Albert Tian
<[email protected]>, Pankaj Garg <[email protected]>, Pankaj
Garg <[email protected]>, Tom Herbert <[email protected]>, Jesse
Gross <[email protected]>, Erik Nordmark <[email protected]>, Lawrence
Kreeger <[email protected]>, Erik Nordmark <[email protected]>



A new version of I-D, draft-rtg-dt-encap-02.txt
has been successfully submitted by Erik Nordmark and posted to the
IETF repository.

Name:           draft-rtg-dt-encap
Revision:       02
Title:          Encapsulation Considerations
Document date:  2015-05-21
Group:          Individual Submission
Pages:          41
URL:            https://www.ietf.org/internet-drafts/draft-rtg-dt-encap-02.txt
Status:         https://datatracker.ietf.org/doc/draft-rtg-dt-encap/
Htmlized:       https://tools.ietf.org/html/draft-rtg-dt-encap-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-rtg-dt-encap-02

Abstract:
   The IETF Routing Area director has chartered a design team to look at
   common issues for the different data plane encapsulations being
   discussed in the NVO3 and SFC working groups and also in the BIER
   BoF, and also to look at the relationship between such encapsulations
   in the case that they might be used at the same time.  The purpose of
   this design team is to discover, discuss and document considerations
   across the different encapsulations in the different WGs/BoFs so that
   we can reduce the number of wheels that need to be reinvented in the
   future.


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




_______________________________________________
Rtg-dt-encap-considerations mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations



_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to