Re: draft-ietf-ccamp-gmpls-sonet-sdh-extensions-00.txt query

[Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>]

Hi,

Just notice that 

     Note 2: when requesting a transparent STM-N/STS-N signal 
     limited to a single contiguously concatenated VC-4-Nc/STS-Nc-
     SPE, the signal type must be STM-N/STS-N, RCC with flag 1 and 
     NCC set to 1.

The reference you have made applies to non-transparent signals.

Regards,
Dimitri.

"Saha, Sayandeb" wrote:
> 
> Shouldn't the following examples in draft
> draft-ietf-ccamp-gmpls-sonet-sdh-extensions-00.txt
> 
> 3. An STS-48c signal with LOH DCC and E2 transparency is formed by the
> application of RCC with flag 1, NCC with value 1, NVC with value 0, MT with
> value 1 and T with flag 5 and 10 to an STS-48 Elementary Signal.
> 
> be
> 
> An STS-48c signal with LOH DCC and E2 transparency is formed by the
> application of RCC with flag 1, NCC with value 16, NVC with value 0, MT with
> value 1 and T with flag 5 and 10 to an STS-3c SPE elementary signal,
> according to  the following ...
> 
> "when requesting a SONET STS-Nc SPE with N=3*X, the elementary signal to use
> must always be an STS-3c SPE signal type and the value of NCC must always be
> equal to X. This allows also facilitating the interworking between SONET and
> SDH. In particular, it means that the contiguous concatenation of three
> STS-1 SPEs cannot not be requested because according to this specification,
> this type of signal must be coded using the STS-3c SPE signal type. "
> 
> in the draft-ietf-ccamp-gmpls-sonet-sdh-02.txt .
> There's a similar problem with example 4 too.
> -Sayan
begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard