RE: [AVT] Re: Clearmode definition.

> Yaakov,
> One of the cases you mention include an RTP encapsulation of 
> Nx64. Unless you have already done so, I recommend you 
> register a MIME for it and allow its session-by-session 
> negotiation using SDP, H.245 or other means. My guess from 
> having read the PWE3 drafts in the past is that you are 
> limiting the application to a provisioned RTP Nx64 session. 
> While that is adequate in some applications, others will 
> require/prefer the signaled establishment of Nx64 sessions.

Rajesh, 

Since this is a PW protocol, it works in the PWE fashion.
Either the PW is manually provisioned, or it is set up
using the PW control protocol. 

In either case it is not envisioned that this connection
will be set-up and torn-down on a "session per session" basis,
just as a T1 or E1 is not torn-down after a phone conversation.

This is another difference between what we are doing in PWE3,
and the typical AVT method of working.

The point of my previous email was that even if it is decided
that PWE is a proper place to standardize methods for
transport of N*64 flows over IP, their treatment at PWE3
may not be what you are looking for.

In particular, MIME types and use of SDP are entirely
alien to the PWE3 way of doing things.

Hence if you have a need for an RTP encapsulation of N*64k, 
I would suggest that the AVT WG look into it,
trying to keep the encapsulation compatible with the
appropriate PWE draft.

Y(J)S

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