List Info

Thread: RFC 4923 on Quality of Service (QoS) Signaling in a Nested Virtual Private Network




RFC 4923 on Quality of Service (QoS) Signaling in a Nested Virtual Private Network
country flaguser name
United States
2007-08-15 18:10:43
A new Request for Comments is now available in online RFC
libraries.

        
        RFC 4923

        Title:      Quality of Service (QoS) Signaling 
                    in a Nested Virtual Private Network 
        Author:     F. Baker, P. Bose
        Status:     Informational
        Date:       August 2007
        Mailbox:    fredcisco.com, 
                    pratik.boselmco.com
        Pages:      38
        Characters: 92632
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:   
draft-ietf-tsvwg-vpn-signaled-preemption-02.txt

        URL:        http://www.
rfc-editor.org/rfc/rfc4923.txt

Some networks require communication between an interior and
exterior
portion of a Virtual Private Network (VPN) or through a
concatenation
of such networks resulting in a nested VPN, but have
sensitivities
about what information is communicated across the boundary,
especially
while providing quality of service to communications with
different
precedence.  This note seeks to outline the issues and the
nature of
the proposed solutions based on the framework for Integrated
Services
operation over Diffserv networks as described in RFC 2998. 
This memo provides information for the Internet community.

This document is a product of the Transport Area Working
Group
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the
Internet community. 
It does not specify an Internet standard of any kind.
Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST
list.
Requests to be added to or deleted from the IETF
distribution list
should be sent to IETF-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained
by sending
an EMAIL message to rfc-infoRFC-EDITOR.ORG with the
message body 

help: ways_to_get_rfcs. For example:

        To: rfc-infoRFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to
either the
author of the RFC in question, or to RFC-ManagerRFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are
for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITORRFC-EDITOR.ORG.  Please consult RFC 2223,
Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-distmailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )