[CCAMP] FW: New Version Notification for draft-ietf-ccamp-interconnected-te-info-exchange-01.txt

["Adrian Farrel" <[e-mail]>]

As noted in the CCAMP meeting in HI [1] a few minor edits were stored up from before adoption of this document. This revision makes those changes.

You'll find:

Section 4.3
Added a view words about RFC 5623.

Section 8 final para
Small change in wording to soften the meaning and deliver the original intent.

Update for publication of RFC 7399.


Open issues still remaining (per [1])

- Should this I-D be moved to Informational?
- Missing sections
   5.4 Considerations for Dynamic Abstraction
   5.6 Addressing Considerations
   11 manageability Considerations
   12 Security Considerations

Adrian

[1] http://www.ietf.org/proceedings/91/slides/slides-91-ccamp-2.pptx slide 19

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> Sent: 20 November 2014 15:38
> To: Xian Zhang; Daniele Ceccarelli; George Swallow; George Swallow; Adrian
> Farrel; Nabil Bitar; John Drake; Xian Zhang; Daniele Ceccarelli; Adrian Farrel; John
> Drake; Dr. Nabil N. Bitar
> Subject: New Version Notification for draft-ietf-ccamp-interconnected-te-info-
> exchange-01.txt
> 
> 
> A new version of I-D, draft-ietf-ccamp-interconnected-te-info-exchange-01.txt
> has been successfully submitted by Adrian Farrel and posted to the
> IETF repository.
> 
> Name:		draft-ietf-ccamp-interconnected-te-info-exchange
> Revision:	01
> Title:		Problem Statement and Architecture for Information Exchange
> Between Interconnected Traffic Engineered Networks
> Document date:	2014-11-20
> Group:		ccamp
> Pages:		56
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-ccamp-interconnected-
> te-info-exchange-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-ccamp-interconnected-te-
> info-exchange/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-ccamp-interconnected-te-info-
> exchange-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-interconnected-te-
> info-exchange-01
> 
> Abstract:
>    In Traffic Engineered (TE) systems, it is sometimes desirable to
>    establish an end-to-end TE path with a set of constraints (such as
>    bandwidth) across one or more network from a source to a destination.
>    TE information is the data relating to nodes and TE links that is
>    used in the process of selecting a TE path.  The availability of TE
>    information is usually limited to within a network (such as an IGP
>    area) often referred to as a domain.
> 
>    In order to determine the potential to establish a TE path through a
>    series of connected networks, it is necessary to have available a
>    certain amount of TE information about each network.  This need not
>    be the full set of TE information available within each network, but
>    does need to express the potential of providing TE connectivity. This
>    subset of TE information is called TE reachability information.
> 
>    This document sets out the problem statement and architecture for the
>    exchange of TE information between interconnected TE networks in
>    support of end-to-end TE path establishment.  For reasons that are
>    explained in the document, this work is limited to simple TE
>    constraints and information that determine TE reachability.
> 
> 
> 
> 
> 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