RE: [AVT] Re: Clearmode definition.

> --> Rajesh Kumar <rkumar@cisco.com> writes:
> > Are there plans to address N x 64 clear mode (N > 1) in 
> > draft-ietf-avt-rtp-clearmode-04.txt ?
> > 
> > One method might be to have N as a MIME parameter.
> > 
> > I recommend that we do.
> 
> No. This is explicitly out of scope of AVT, and will be 
> addressed in the PWE3 working group.

N*DS0 (i.e. N 64Kbps timeslots) with or without CAS
is defined in the PWE3 TDM requirements draft as a structured TDM
service.

Right now in PWE we have three TDM drafts:

1) The standards track one is SAToP (Structure Agnostic TDM over
Packet),
but this only handles full T1, E1, E3 or T3 trunks
(whether structured or not). Thus this doesn't address N*64.

2) CESoPSN - candidiate informational RFC
This draft can handle N*DS0 by encapsulating one or more frames or N
timeslots
per packet, with or without RTP.

3) TDMoIP - candidate informational RFC
This draft can handle N*DS0 by using AAL1 which appends
pointers to identify the first timeslot. 
If the 64K channels are carrying HDLC data, there is a mode
which suppresses idle flags.

As you can see, the treatment of N*DS0 is only in the informational
drafts,
not in the standards track one.

The current suggestion for communicating N is via the PWE control
protocol,
where there is a parameter called CEP/TDM bit rate.

Y(J)S

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt