[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [PWE3] Setup of TDM PWs: Follow-up for the Seoul meeting

 
> Luca, Mark and all,
> Following my presentation at the Seoul WG session and our 
> discussions there, I'd like to ask you to update the PWE3 
> IANA Allocation draft (it expires in April anyway:-) like following:
> 
> 1. In Section 2 (PW Type), continume the list of PW Types 
> like following:
> ...
> 0x0010   SONET/SDH Circuit Emulation over Packet (CEP) -- 
> this is the last
> entry so far
> 0x0011   Structure-agnostic E1 over Packet (SAToP)
> 0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP) 
> 0x0013   Structure-agnostic E3 over Packet (SAToP) 
> 0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP) 
> 0x0015   Structure-aware Basic NxDS0 (CESoPSN, TDMoIP)
> 0x0016   Structure-aware Trunk-specific NxDS0 with CAS (CESoPSN,
TDMoIP)

I agree in principle, but we should separate the CESoPSN and TDMoIP
cases.

> Please note that this list corresponds to the list of 
> services in the TDM Requirements draft. Different MF formats 
> for NxDS0 with CAS will be accommodated in the next version 
> of the TDM Control Protocol Extensions draft.
> 
> 2. In Section 3 (Interface Parameters field), please continue 
> the list of Interface Parameters like following:
> ...
>        0x09         2       Fragmentation indicator -- this 
> is the last entry so far
>        0x10    4, 8 or 12   TDM Options [ref]
> 
> In addition, please change the name of the existing interface 
> parameter from CEP Payload Bytes to CEP/TDM Payload Bytes in 
> the corresponding entry.
> It would be really nice if you could accommodate this change 
> also in the PWE3 Control Protocol draft.

I think calling it TDM is enough
(the TDM requirements draft defines TDM as including SONET/SDH!)

 Y(J)S

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3