ASON-Compatible Signaling

1
ASON-Compatible Signaling
2
Current Status

• draft-ietf-ccamp-gmpls-rsvp-te-ason-04.txt
• No real progress for around a year
• Draft tries to do two things
• Point out how existing RFCs and I-Ds can be used
  to meet the requirements of ASON signaling
• Requirements in RFC 4139
• Define protocol extensions to fill the gaps
• Propose to split the I-D along these lines
• We need to do both items according to charter
• There is interest in implementation

3
Filling the Gaps

• The gap is support for Calls in GMPLS signaling
• OIF/RFC3474 approach considered unacceptable
• Designed for UNI not NNI
• Piggy-backs call information on Path message
• Requires retention of call state within network
• Does not allow connection-free calls
• Unclear how connections are added to or removed
  from calls

4
GMPLS Call Support

• Use Notify messages
• Can be targeted to Call Controllers
• End points and domain boundaries
• Notify message carries full details of call
• Path message can associate a connection with a
  call
• Allows independent call/connection setup and
  management
• Cleaned-up document at http//www.olddog.co.uk/mi
  ssing.htm
• Aim to publish and implement at once
• Last call soon

5
Applicability Statement

• The other piece of the work
• Applicability of GMPLS signaling to the
  requirements of an ASON architecture
• Short draft based on documented requirements
• Pointers to RFCs and I-Ds
• Extract material from existing draft
• Update and polish
• Add information for support of calls
• Just a documentation task