INTERNATIONAL TELECOMMUNICATION UNION

COM 15 – LS 38 – E

TELECOMMUNICATION
STANDARDIZATION SECTOR

STUDY PERIOD 2001-2004

 

English only

Original: English

Question(s):

14/15

20-31 January 2003

LIAISON STATEMENT

Source:

ITU-T SG15

Title:

Input on SDH and OTN Discovery Mechanisms

To:

IETF CCAMP WG and Sub-IP Area Directors

Approval:

Agreed to at SG 15 meeting, Geneva, 20 –31 January 2003

For:

Action

Deadline:

March 2003

Contact:

Hing-Kam Lam

Lucent Technologies

USA

Tel: +1 732-949-8338

Fax: +1 732-949-5055

Email: hklam@lucent.com

Contact:

 

 

 

Tel:

Fax:

Email:

 

Q.14/15 would like to inform the IETF CCAMP Working Group that SG 15 has consented G.7714.1, "Protocol for Automatic Discovery in SDH and OTN Networks".  It is our understanding that questions have been raised in the CCAMP WG discussions regarding the usage of the Jx Trace Bytes in SDH for Discovery purposes.  We believe that this document will help in the mutual understanding of the application of the SDH and OTN overhead to the Discovery process. 

 

1.       We would like the IETF to consider the formats proposed in this document, and invite the IETF to define, if necessary, an additional format for GMPLS to use the SDH and OTN Layer Adjacency Discovery process. We will agree on a specific code-point for this format. Note that the formats are defined according to the architectural requirements of G.7714.1. (Section 8)

 

The in-band discovery message includes at least the <TCP-ID> and optionally the <DA DCN ID> or a handle which can be mapped to an address. Both <TCP-ID> and <DA DCN ID> are defined in G.7714.1. 

 

NOTE: TCP in this context stands for Termination Connection Point, as defined in Recommendation G.805.

 

The information elements for the out-of-band discovery response message associated with the above in-band discovery message are defined in G.7714.1. The control plane protocol specific format is outside of the scope of G.7714.1. We invite IETF to propose the message format suitable to exchange these information elements.

 

2.      An out-of-band discovery response message exchanged over the Data Communication Network (DCN) includes at least the following information elements: <local TCP-ID>, <remote TCP-ID>, [<local TCP-ID fully qualified name>], [<local DA DCN ID>], [<remote DA DCN ID>]. The remote DA DCN Address is optional in case of global scope name server. It is assumed that the [<TCP-ID fully qualified name>] can take one of the well-known IPv4 addressing, IPv6 addressing, NSAP, etc. space value. (referenced in Section 8)

 

The exchange of the above mentioned out-of-band message does not preclude any other prior GMPLS message exchange.

 

The establishment of the control channel (referenced in Appendix III of G.7714.1) can be mapped to the procedure defined in Section 3 of LMP (draft-ietf-ccamp-lmp-07.txt).

 

The consented new Recommendation G.7714.1 can be found from the ccamp link from at the following link:

 

ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/index.html

 

Attention: Some or all of the material attached to this liaison statement may be subject to ITU copyright. In such a case, this will be indicated in the individual document.

Such a copyright does not prevent the use of the material for its intended purpose, but it prevents the reproduction of all or part of it in a publication without the authorization of ITU.

 

________________