Transcript draft-zhang-ccamp-general-constraints-ospf-ext-00

OSPF-TE Extensions for General
Network Element Constraints
draft-zhang-ccamp-general-constraints-ospf-ext-00
Fatai Zhang ([email protected])
Young Lee([email protected])
Jianrui Han([email protected])
Greg Bernstein ([email protected])
Yunbin Xu ([email protected])
79th IETF – Beijing China, November 2010
Changes from 03.txt
• This “new” draft is from [draft-zhang-ccamp-rwawson-routing-ospf-03.txt] “OSPF Extensions in
Support of RWA in WSONs”
• The draft was renamed as “OSPF Extensions for
General Network Element Constraints”
• Re-described the draft in more general way
– Not just aim at WSON specific technology (e.g.,
Change the term wavelength to label)
79th IETF – Beijing China, November 2010
Renaming Explanation
• History story
– Lots of discussion
– Following the WG’s endorsement at IETF78th
meeting
– This draft just focuses on general stuff
• Alignment with [General Constraint Encode]
– The protocol extensions are applicable not only to
WSON, but also to a wider range of
technologies(e.g., TDM networks with potential
constraints)
79th IETF – Beijing China, November 2010
Relationship of the Related Drafts
WSON Information Model
(draft-ietf-ccamp-rwa-info)
General Constraint Encode
WSON Specific Encode
(draft-ietf-ccamp-rwa-wson-encode )
(draft-ietf-ccamp-general-constraint-encode )
draft-zhang-ccampgeneral-constraints-ospfext-00
draft-ietf-ccamp-wsonsignal-compatibilityospf-02
Follows the Gen-Encode
draft strictly
Follows the WSON-Encode
draft strictly
OSPF Extensions
79th IETF – Beijing China, November 2010
draft-peloso-ccampwson-ospf-oeo-02
OSPF Extensions
• Node Attribute LSA
– Node Attribute Top-TLV (TLV type: 5)
• Node IPv4/IPv6 Local Address sub-TLV
• Connectivity Matrix sub-TLV(s) (static)
– Format is defined in [GEN-Encode]
• TE link LSA
– Link Top-TLV (TLV type: 2)
• Link sub-TLVs defined in [RFC3630] and [RFC4203]
– Link ID
– Link local/remote identifiers
– …
• Link sub-TLVs defined in [GEN-Encode]
– Port Label Restrictions (static)
– Available Labels (dynamic)
– Shared Backup Labels (dynamic)
79th IETF – Beijing China, November 2010
Routing Procedures
• Static information and dynamic information of one TE link may be
contained in two separate Opaque LSAs
– Link LSA 1 (static)
•
•
•
•
Link ID
…
Port Label Restrictions
…
– Link LSA 2 (dynamic)
•
•
•
•
•
Link ID
…
Available Labels
Shared Backup Labels
…
• Connectivity Matrix is a kind of static information of a node
– This information can be advertised in an LSA carrying the Connectivity
Matrix sub-TLV(s) in a Node Attribute top-TLV.
• For static information, it can be updated with a lower frequency to
avoid unnecessary updates.
79th IETF – Beijing China, November 2010
Discussions
• Re-use Node Attribute TLV vs New Top TLV
– “Connectivity Matrix” is static info like the IP local address
defined [RFC5786]
– “Connectivity Matrix” and IP local address can be defined
as sub-TLVs of Node Attribute TLV, and comply with the
existing rules defined in [RFC5786]
– It is better to reuse the existing things
• It does not prevent to use a new TOP TLV when
needed in WSON specific OSPF extension, but
it is out of the scope of this draft
79th IETF – Beijing China, November 2010
Next Steps
•Adopt it as a WG document
•Refine it based on the feedback from the
meeting or mailing list
79th IETF – Beijing China, November 2010