Re: [PWE3] Transport of CAS over CESoPSN [RFC 5086]

[Javi <[e-mail]>]

Yaakov Stein escribió:
>
> > b) If the mechanism 5.3 necessary, why is not covered by the RFC 5087
> > (TDMoIP) for AAL.1?
>
> /[[Sasha]] I cannot answer that, but I've added Yaakov Stein to the CC 
> list./
>
> Sorry for being out of email contact for a while.
>
> If I understand the question correctly, you are asking why TDMoIP/AAL1 
> does not
>
> add a CAS substructure similar to CESoPSN. This is because the AAL1 
> already has one
>
> (it's called AAL1 structured with CAS).
>
The question was: CESoPSN (RFC 5086) defines two mechanism to transport 
CAS signalling:

  + "5.3.  Extending Basic NxDS0 Services with CE Application 
Signaling":  it may transport the state signalling of CEs, e.g., CAS for 
the telephony applications.
  + "5.4.  Trunk-Specific NxDS0 Services with CAS (CAS substructure)": 
it transport CAS signalling for the telephony applications.

However, TDMoIP AAL1 (RFC 5087) only provides the second one. Why is 
"Extending Basic NxDS0 Services with CE Application Signaling" not 
defined by RFC 5087?

Evenmore, for CESoPSN[RFC5086], RFC 5611 only mentions "CESoPSN basic 
mode" (0x0015) and "trunk-specific CESoPSN service with CAS" (0x0017), 
but not "5.3.  Extending Basic NxDS0 Services with CE Application 
Signaling". Why?

Javi