Subject: RE: [NSIS] RE: I-D ACTION:draft-ash-nsis-vertical-interface-00.tx t

From: "Nguyen, An" <[email-masked]>
Date: Tue, 9 Aug 2005 15:10:59 -0400

John,

I agreed this draft would be of interest to the IEPREP.

An 

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Saturday, July 30, 2005 4:50 AM
To: [email-masked]; [email-masked]
Subject: RE: [NSIS] RE: I-D
ACTION:draft-ash-nsis-vertical-interface-00.txt 

Jerry,

I had a quick reading of this draft, it looks fairly interesting, but I
would need to 
re-read and analysis the scenario in a bit more detail.

The scope of the document is somewhat confusing though. I orignally thought
this would be a more general solution, for example, proposing how to use
NSIS QoS NSLP with SIP signaling, but you do focus on the ETS case.  Perhaps
better clarifying this in the revision would helpful. Depending upon what
your target is, illustrating the basic QoS NSLP operation for consumer
VOIP, without such a specific network deployment, "DiffServ-enabled MPLS
traffic 
engineering (DSTE) [RFC3564] tunnel ..." for example, would be a good idea.

I'd suggest for a revision that you include a terminology section, as there 
are a lot of acronyms, and terminology that are not immediately
recognizable.

Any consideration on discussing this draft in ieprep, at least to verify
the usecase?  This seems like it would be of interest there.

thanks,
John

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]On Behalf Of
> ext Ash, Gerald R (Jerry), ALABS
> Sent: 12 July, 2005 00:38
> To: [email-masked]
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: [NSIS] RE: I-D 
> ACTION:draft-ash-nsis-vertical-interface-00.txt 
> 
> 
> Hi All,
> 
> Please review and comment on the draft 'User Application-to-User Plane
> Vertical Interface'
> (http://www.ietf.org/internet-drafts/draft-ash-nsis-vertical-i	
> nterface-0
> 0.txt).  
> 
> The draft proposes requirements for communicating QoS
> parameters/attributes between the user application layer down to the
> user plane to create an NSIS session.  For this discussion, SIP is the
> signaling protocol assumed at the user application layer and QoS-NSIS
> signaling layer protocol (QoS-NSLP) is assumed at the user 
> plane layer.
> 
> Thanks,
> Jerry
> 
> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]] On Behalf Of
> [email-masked]
> Sent: Monday, July 11, 2005 3:50 PM
> To: [email-masked]
> Subject: I-D ACTION:draft-ash-nsis-vertical-interface-00.txt 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: User Application-to-User Plane Vertical
> Interface
> 	Author(s)	: J. Ash, et al.
> 	Filename	: draft-ash-nsis-vertical-interface-00.txt
> 	Pages		: 11
> 	Date		: 2005-7-11
> 	
>    This draft describes a mechanism to map QoS requirements from the
>    User application layer down to the user plane to create an NSIS
>    session.  This 'vertical signaling interface' between the user
>    application layer and user plane is needed to communicate these QoS
>    requirements, such as flow priority values, to user plane network
>    elements.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ash-nsis-vertical-in
terface-00
.txt

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis