Received: from cnri by ietf.org id aa23128; 5 Sep 97 18:22 EDT Received: from ietf.org (ietf.org [132.151.1.19]) by cnri.reston.va.us (8.8.5/8.7.3) with SMTPid SAA07978 for ; Fri, 5 Sep 1997 18:25:31 -0400 (EDT) Received: from ietf.org by ietf.org id aa23115; 5 Sep 97 18:22 EDT Received: from pilgrim.cisco.com by ietf.org id aa23111; 5 Sep 97 18:22 EDT Received: from tdowney-pc.cisco.com (ch-dhcp207-196.cisco.com [171.69.207.196]) by pilgrim.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id SAA03811; Fri, 5 Sep 1997 18:22:26 -0400 (EDT) Message-Id: <3.0.32.19970905180936.0074cd04@pilgrim.cisco.com> X-Sender: tdowney@pilgrim.cisco.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 05 Sep 1997 18:09:39 -0400 To: iesg@ietf.org Sender: iesg-request@ietf.org From: Tom Downey Subject: tag switching patents Cc: mpls@external.cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Recently, I have been asked questions regarding my December 1996 email on Cisco's patents and licensing for tag switching. In December, I noted that if any patents issued to Cisco are required to practice any standards arising from the MPLS IETF standards process, Cisco intends to disclose those patents and license them under openly specified and non-discriminatory terms, for no fee. The recent questions have asked what the terms will be. If any patents issued to Cisco are required to practice any standards arising from the MPLS IETF standards process, Cisco intends to license those patents under the terms and conditions that were used by HP in RFC 1988. As noted in December, our goal is to support and encourage the standardization efforts within the IETF and to achieve a multi-vendor concensus on a set of protocols for this new technology area.  From daemon Wed Nov 19 10:25:22 1997 Delivery-Date: Wed, 19 Nov 1997 10:35:24 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id KAA28085 for ietf-123-outbound.10@ietf.org; Wed, 19 Nov 1997 10:25:10 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id KAA27849; Wed, 19 Nov 1997 10:19:05 -0500 (EST) Message-Id: <199711191519.KAA27849@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-label-encaps-00.txt Date: Wed, 19 Nov 1997 10:19:05 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : MPLS Label Stack Encoding Author(s) : D. Farinacci, D. Tappan, T. Li, G. Fedorkow, A. Conta, Y. Rekhter, E. Rosen Filename : draft-ietf-mpls-label-encaps-00.txt Pages : 19 Date : 18-Nov-97 ''Multi-Protocol Label Switching (MPLS)'' [1,2,3] requires a set of procedures for augmenting network layer packets with ''label stacks'', thereby turning them into ''labeled packets''. Routers which support MPLS are known as ''Label Switching Routers'', or ''LSRs''. In order to transmit a labeled packet on a particular data link, an LSR must support an encoding technique which, given a label stack and a network layer packet, produces a labeled packet. This document specifies the encoding to be used by an LSR in order to transmit labeled packets on PPP data links and possibly on other data links as well. On some data links, the label at the top of the stack may be encoded in a different manner, but the techniques described here MUST be used to encode the remainder of the label stack. This document also specifies rules and procedures for processing the various fields of the label stack encoding. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-label-encaps-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-mpls-label-encaps-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-mpls-label-encaps-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971118111135.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-label-encaps-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-label-encaps-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971118111135.I-D@ietf.org> --OtherAccess-- --NextPart-- From daemon Mon Dec 1 13:33:49 1997 Delivery-Date: Mon, 01 Dec 1997 13:40:56 -0500 Return-Path: daemon Received: (from daemon@localhost) by ns.ietf.org (8.8.7/8.8.7a) id NAA04564 for ietf-123-outbound.10@ietf.org; Mon, 1 Dec 1997 13:33:37 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id NAA03458; Mon, 1 Dec 1997 13:27:31 -0500 (EST) Message-Id: <199712011827.NAA03458@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-framework-02.txt Date: Mon, 01 Dec 1997 13:27:31 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : A Framework for Multiprotocol Label Switching Author(s) : R. Callon, G. Swallow, N. Feldman, A. Viswanathan, P. Doolan, A. Fredette Filename : draft-ietf-mpls-framework-02.txt Pages : 65 Date : 26-Nov-97 This document discusses technical issues and requirements for the Multiprotocol Label Switching working group. This is an initial draft document, which will evolve and expand over time. It is the intent of this document to produce a coherent description of all significant approaches which were and are being considered by the working group. Selection of specific approaches, making choices regarding engineering tradeoffs, and detailed protocol specification, are outside of the scope of this framework document. Note that this document is at an early stage, and that most of the detailed technical discussion is only in a rough form. Additional text will be provided over time from a number of sources. A small amount of the text in this document may be redundant with the proposed protocol architecture for MPLS. This redundancy will be reduced over time, with the overall discussion of issues moved to be in this document, and the selection of specific approaches and specification of the protocol contained in the protocol architecture and other related documents. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-framework-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-mpls-framework-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-mpls-framework-02.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971126171113.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-framework-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-framework-02.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971126171113.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Tue Dec 30 12:27:58 1997 Delivery-Date: Tue, 30 Dec 1997 12:34:22 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id MAA07471 for ietf-123-outbound.10@ietf.org; Tue, 30 Dec 1997 12:27:02 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id LAA05158; Tue, 30 Dec 1997 11:18:45 -0500 (EST) Message-Id: <199712301618.LAA05158@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-fr-00.txt Date: Tue, 30 Dec 1997 11:18:44 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Use of Label Switching on Frame Relay Networks Specification Author(s) : A. Malis, A. Conta, P. Doolan Filename : draft-ietf-mpls-fr-00.txt Pages : 19 Date : 29-Dec-97 This document defines the model and generic mechanisms for Multiprotocol Label Switching on Frame Relay networks. A Multiprotocol Label Switching Architecture is described in [ARCH]. MPLS enables the use of Frame Relay Switches as Label Switching Routers (LSRs). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-fr-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-mpls-fr-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-mpls-fr-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971229161857.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-fr-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-fr-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971229161857.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-ppp@merit.edu Sun Feb 8 11:24:27 1998 Delivery-Date: Sun, 08 Feb 1998 11:24:28 -0500 Return-Path: owner-ietf-ppp@merit.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id LAA02933 for ; Sun, 8 Feb 1998 11:24:26 -0500 (EST) Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA00596 for ; Sun, 8 Feb 1998 11:27:10 -0500 (EST) Received: from localhost (daemon@localhost) by merit.edu (8.8.7/8.8.5) with SMTP id LAA21590; Sun, 8 Feb 1998 11:12:28 -0500 (EST) Received: by merit.edu (bulk_mailer v1.5); Sun, 8 Feb 1998 11:08:24 -0500 Received: (from majordom@localhost) by merit.edu (8.8.7/8.8.5) id LAA21558 for ietf-ppp-outgoing; Sun, 8 Feb 1998 11:08:23 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by merit.edu (8.8.7/8.8.5) with ESMTP id LAA21554 for ; Sun, 8 Feb 1998 11:08:19 -0500 (EST) Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id KAA09548; Sun, 8 Feb 1998 10:57:53 -0500 (EST) Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with SMTP id KAA00882; Sun, 8 Feb 1998 10:57:25 -0500 (EST) Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA17157; Sun, 8 Feb 98 10:57:03 EST for int-serv@isi.edu Received: from ndoraswa.corpeast.baynetworks.com ([132.245.112.95]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with SMTP id AAA13444; Sun, 8 Feb 1998 10:55:55 -0500 Message-Id: <3.0.32.19980208105656.00b7bb68@bl-mail1.corpeast.baynetworks.com> X-Sender: ndoraswa_pop@bl-mail1.corpeast.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 08 Feb 1998 10:56:58 -0500 To: ipsec@tis.com, mpls@external.cisco.com, ietf-ppp@merit.edu, int-serv@isi.edu From: Naganand Doraswamy Subject: VPN mailing list Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_886971418==_" Sender: owner-ietf-ppp@merit.edu --=====================_886971418==_ Content-Type: text/plain; charset="us-ascii" I have created VPN mailing list and attached a proposed charter. I would like to start discussion on what the charter of working group should be and what problems we should be working on. We intend to have another BOF at IETF but this time we need to nail down the charter. --=====================_886971418==_ Content-Type: text/plain; charset="us-ascii" VPN BOF ------- Proposed Chairs --------------- Naganand Doraswamy (naganand@baynetworks.com) Robert Moskowitz (rgm3@icsa.net) Area Directors -------------- Thomas Narten (narten@raleigh.ibm.com) Jeffrey Burgan (burgan@home.net) Area Advisor ------------ TBD Mailing Lists ------------- Discussions: vpn@baynetworks.com subscription: majordomo@baynetworks.com. In the body of the message say: subscribe vpn Description of VPN BOF ---------------------- Virtual Priavate Networking (VPN) is a way of extending a private network seamlessly over a public network. However, this raises various issues such as security, Addressing, Quality of Service to name a few as the traffic belonging to the private network traverses a public network. VPN model can be one of many. An organization can build its VPN. An ISP can build and maintain a VPN of an organization. VPN can exist between organizations (extranets). There is a need to define mechanisms to achieve these capabilies. Some of the issues that needs to be addressed are: 1. Security: Security can be achived by restricting the packet flowing in an out of a VPN. In addition the packets can also be encrypted and authenticated. 2. How to provide Quality of Service/Class of service for packets flowing between the edges. In this case, we may not be worried about providing end to end QoS but only between edges. 3. How to handle Network Address Translation issues. Even though NAT's are a kludge, it has been deployed widely and there is a need to address this issue properly. Should we consider extending the concept of private addressing over the Internet? 4. Ease of configuration. 5. Reliability. 6. Management The goals of the VPN BOF are: 1. Decide if there is a need to form a working group to solve some or all of the problems above. 2. Which of the problems above should be addressed by the working group. 3. What will the working group produce. In our opinion, we need to interact with other working groups such as IPsec working group, NAT working group, int-serv working group, and probably routing working group to solve some or all of the problems above. 4. What other problems need to be solved for succesful deployment of VPN's. --=====================_886971418==_ Content-Type: text/plain; charset="us-ascii" --Naganand ----------------------------------------------------------------- Naganand Doraswamy (978)916-1323 (O) Bay Architecture Lab (978)670-0620 (Fax) 3 Federal St, Mail Stop BL3-03 Billerica, MA 01821 --=====================_886971418==_-- From owner-ietf-ppp@merit.edu Mon Feb 16 12:59:32 1998 Delivery-Date: Mon, 16 Feb 1998 12:59:32 -0500 Return-Path: owner-ietf-ppp@merit.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id MAA01330 for ; Mon, 16 Feb 1998 12:59:31 -0500 (EST) Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA02996 for ; Mon, 16 Feb 1998 13:02:10 -0500 (EST) Received: from localhost (daemon@localhost) by merit.edu (8.8.7/8.8.5) with SMTP id MAA10575; Mon, 16 Feb 1998 12:41:34 -0500 (EST) Received: by merit.edu (bulk_mailer v1.5); Mon, 16 Feb 1998 12:41:01 -0500 Received: (from majordom@localhost) by merit.edu (8.8.7/8.8.5) id MAA10528 for ietf-ppp-outgoing; Mon, 16 Feb 1998 12:41:00 -0500 (EST) Received: from mail.sprint.com (mail.sprint.com [208.4.29.129]) by merit.edu (8.8.7/8.8.5) with ESMTP id MAA10514 for ; Mon, 16 Feb 1998 12:40:37 -0500 (EST) Received: from sii01.mail.sprint.com ([192.251.141.141]) by bastion.mail.sprint.com with ESMTP id <16284>; Mon, 16 Feb 1998 11:37:24 -0600 Received: from x400-gw.mail.sprint.com by sii01.mail.sprint.com (X.400 to RFC822 Gateway); Mon, 16 Feb 1998 10:51:08 -0600 X400-Received: by mta MTASprint in /c=US/admd=TELEMAIL/prmd=Sprint/; Relayed; 16 Feb 1998 10:50:54 -0600 X400-Received: by /c=US/admd=TELEMAIL/prmd=Sprint/; Relayed; 16 Feb 1998 10:50:54 -0600 X400-MTS-Identifier: [/c=US/admd=TELEMAIL/prmd=Sprint/; 0068D34E86E6E0EC-MTASprint] Content-Identifier: 0068D34E86E6E0EC Content-Return: Allowed X400-Content-Type: P2-1988 ( 22 ) Conversion: Allowed Original-Encoded-Information-Types: IA5-Text Disclose-Recipients: Prohibited Alternate-Recipient: Allowed X400-Originator: Linn.Johnson@mail.sprint.com X400-Recipients: non-disclosure; Message-Id: <"0068D34E86E6E0EC*/c=us/admd=Telemail/prmd=Sprint/o=QM/ou=QM(u)1850(u)1/s=Johnson/g=Linn/"@MHS> Date: Mon, 16 Feb 1998 10:50:54 -0600 From: Linn Johnson To: Naganand Doraswamy (IPM Return requested Receipt notification requested), ietf-ppp (IPM Return requested Receipt notification requested), int-serv (IPM Return requested Receipt notification requested), ipsec (IPM Return requested Receipt notification requested), mpls (IPM Return requested Receipt notification requested) Subject: RE>VPN mailing list Sender: owner-ietf-ppp@merit.edu Reply to: RE>VPN mailing list How do I get off the ietf-ppp mailing list? linn.johnson@mail.sprint.com -------------------------------------- Date: 2/8/98 10:17 To: Linn Johnson From: Naganand Doraswamy I have created VPN mailing list and attached a proposed charter. I would like to start discussion on what the charter of working group should be and what problems we should be working on. We intend to have another BOF at IETF but this time we need to nail down the charter. From adm Fri Feb 20 16:18:29 1998 Delivery-Date: Fri, 20 Feb 1998 16:21:46 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id QAA16133 for ietf-123-outbound.10@ietf.org; Fri, 20 Feb 1998 16:17:02 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id PAA14466; Fri, 20 Feb 1998 15:33:19 -0500 (EST) Message-Id: <199802202033.PAA14466@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-label-encaps-01.txt Date: Fri, 20 Feb 1998 15:33:18 -0500 Sender: scoya@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : MPLS Label Stack Encoding Author(s) : D. Farinacci, T. Li, A. Conta, Y. Rekhter, E. Rosen Filename : draft-ietf-mpls-label-encaps-01.txt Pages : 20 Date : 18-Feb-98 ''Multi-Protocol Label Switching (MPLS)'' [1,2,3] requires a set of procedures for augmenting network layer packets with ''label stacks'', thereby turning them into ''labeled packets''. Routers which support MPLS are known as ''Label Switching Routers'', or ''LSRs''. In order to transmit a labeled packet on a particular data link, an LSR must support an encoding technique which, given a label stack and a network layer packet, produces a labeled packet. This document specifies the encoding to be used by an LSR in order to transmit labeled packets on PPP data links and possibly on other data links as well. On some data links, the label at the top of the stack may be encoded in a different manner, but the techniques described here MUST be used to encode the remainder of the label stack. This document also specifies rules and procedures for processing the various fields of the label stack encoding. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-label-encaps-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-label-encaps-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-mpls-label-encaps-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19980218104138.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-label-encaps-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-label-encaps-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980218104138.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-outbound.10 Tue Feb 24 15:35:17 1998 Delivery-Date: Tue, 24 Feb 1998 15:40:09 -0500 Return-Path: owner-ietf-outbound.10 Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id PAA02513 for ietf-outbound.10@ietf.org; Tue, 24 Feb 1998 15:35:02 -0500 (EST) Received: from gdc.com (gate6.gdc.com [206.97.118.12]) by ns.ietf.org (8.8.7/8.8.7a) with SMTP id PAA02206 for ; Tue, 24 Feb 1998 15:26:16 -0500 (EST) Received: from techmail.gdc.com ([172.16.0.56]) by gate6.gdc.com with ESMTP id <32260>; Tue, 24 Feb 1998 15:29:34 -0500 Received: from avra ([192.168.64.126]) by techmail.gdc.com (8.8.5/8.8.5/NCSHUB-1.6) with SMTP id PAA22776; Tue, 24 Feb 1998 15:26:03 -0500 (EST) Message-ID: <00b801bd4159$91166260$7e40a8c0@avra.gdc.com> Reply-To: "avri doria" From: "avri doria" To: , Cc: Subject: New email list for discussion of GSMP Date: Tue, 24 Feb 1998 14:22:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-7" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 A new email discussion list has been setup for discussing the Generalized Switch Management Protocol (GSMP). The creation of this list at this time is prompted by the recent distribution of a new GSMP protocol specification: ftp://ftp.ietf.org/internet-drafts/draft-rfced-info-ipsilon-00.txt. I have spoken to a few people and find that there is at least a mild level of interest in looking at the GSMP protocol, both as expressed in RFC1987 and in the current I-D, as a candidate for the IETF standardization process. I contacted the AD of the Internet area about setting up a BOF, and received the recommendation that first I should create a mail list to gauge interest. Hence, the list and this announcement. I considered asking the Routing I-D for the BOF as I think that GSMP is an excellent candidate for controlling a remote L2 switch in a LSR. However, since I thought a 'general' GSMP was perhaps useful beyond MPLS, I decided that the Internet area was more appropriate. I would not be adverse, however, to a BOF in the Routing area, or any other area for that matter, if anyone else thought that was a better alternative. As far as the list itself goes, in addition to techno-political discussions on whether it is appropriate to have a BOF, the shape of a WG and charter etc..., I am hoping we can discuss the recent draft. I am especially interested in discussing the protocol's utility for handling multicast switching and the newly added TOS/QoS capabilities. I would also like to discuss adding other features to the protocol. Truth in advertising: I care about GSMP not only because I like the protocol and think it would be a valuable addition to the IETF protocol collection. I also care because I am involved in building a GSMP controlled switch and would very much like for the GSMP protocol it uses to be a standard - or at least in the process of being standardized. Regards, avri From owner-ietf-outbound.10 Tue Feb 24 21:00:17 1998 Delivery-Date: Tue, 24 Feb 1998 21:01:52 -0500 Return-Path: owner-ietf-outbound.10 Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id VAA10805 for ietf-outbound.10@ietf.org; Tue, 24 Feb 1998 21:00:02 -0500 (EST) Received: from gdc.com (gate6.gdc.com [206.97.118.12]) by ns.ietf.org (8.8.7/8.8.7a) with SMTP id UAA10729 for ; Tue, 24 Feb 1998 20:55:21 -0500 (EST) Received: from techmail.gdc.com ([172.16.0.56]) by gate6.gdc.com with ESMTP id <32260>; Tue, 24 Feb 1998 20:58:38 -0500 Received: from avra (esun955.gdc.com [172.16.3.166]) by techmail.gdc.com (8.8.5/8.8.5/NCSHUB-1.6) with SMTP id UAA02887; Tue, 24 Feb 1998 20:55:12 -0500 (EST) Message-ID: <002601bd4187$88d82920$11617392@avra.gdc.com> From: "avri doria" To: , Cc: Subject: GSMP List Date: Tue, 24 Feb 1998 19:51:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Ok, one is really doing a good job when they: a) forget to give subscription instructions on a list announcement b) leaves out a part of the URL for the draft c) gets the name of the protocol wrong Apologies. a) send a request to gsmp-request@psyton.com with subscribe GSMP user@where.whatever in the body of the message. b) ftp://ftp.ietf.org/internet-drafts/draft-rfced-info-ipsilon-gsmp2-00.txt c) it is General Switch Management Protocol. it's me that wants to generalize it. Thanks to the many who advised and corrected me. I am glad so many were interested. a. From adm Fri Mar 6 21:39:06 1998 Delivery-Date: Fri, 06 Mar 1998 21:47:11 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id VAA13104 for ietf-123-outbound.10@ietf.org; Fri, 6 Mar 1998 21:35:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id OAA20359; Fri, 6 Mar 1998 14:44:21 -0500 (EST) Message-Id: <199803061944.OAA20359@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-vcid-atm-00.txt Date: Fri, 06 Mar 1998 14:44:21 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : VCID Notification over ATM link Author(s) : N. Demizu, H. Esaki, K. Nagami, P. Doolan Filename : draft-ietf-mpls-vcid-atm-00.txt Pages : 10 Date : 10-Feb-98 Several label switching schemes have been proposed to integrate Layer 2 and Layer 3. The ATM Label Switching Router (ATM-LSR) is one of the major applications of label switching. Because the ATM layer labels (VPI and VCI) associated with a VC may change on each VC of that VCC, it is not possible to use them to identify a VCC in label binding messages. The concept of Virtual Connection Identifier (VCID) is introduced to solve this problem. VCID has the same value at both ends of a VCC. This document specifies the procedures for the communication of VCID values between neighboring ATM-LSRs that must occur in order to ensure this property. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-vcid-atm-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-vcid-atm-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-vcid-atm-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980305140153.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-vcid-atm-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-vcid-atm-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980305140153.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Fri Mar 13 11:16:36 1998 Delivery-Date: Fri, 13 Mar 1998 11:20:40 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id LAA04561 for ietf-123-outbound.10@ietf.org; Fri, 13 Mar 1998 11:15:03 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id IAA24281; Fri, 13 Mar 1998 08:10:54 -0500 (EST) Message-Id: <199803131310.IAA24281@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-mpls-rsvp-00.txt Date: Fri, 13 Mar 1998 08:10:54 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Use of Label Switching With RSVP Author(s) : B. Davie, Y. Rekhter, A. Viswanathan, S. Blake, V. Srinivasan, E. Rosen Filename : draft-ietf-mpls-rsvp-00.txt Pages : 13 Date : 12-Mar-98 Multiprotocol Label Switching (MPLS) allows labels to be bound to various granularities of forwarding information, including application flows. In this document we present a specification for allocating and binding labels to RSVP flows, and to distributing the appropriate binding information using RSVP messages. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-rsvp-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-rsvp-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980312182636.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-rsvp-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-rsvp-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980312182636.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Wed Apr 8 12:26:33 1998 Delivery-Date: Wed, 08 Apr 1998 12:39:12 -0400 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.5/8.8.7a) id MAA11270 for ietf-123-outbound.10@ietf.org; Wed, 8 Apr 1998 12:25:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id KAA07305; Wed, 8 Apr 1998 10:29:45 -0400 (EDT) Message-Id: <199804081429.KAA07305@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-arch-01.txt Date: Wed, 08 Apr 1998 10:29:41 -0400 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Multiprotocol Label Switching Architecture Author(s) : R. Callon, A. Viswanathan, E. Rosen Filename : draft-ietf-mpls-arch-01.txt Pages : 63 Date : 07-Apr-98 This internet draft specifies the architecture for multiprotocol label switching (MPLS). The architecture is based on other label switching approaches [2-11] as well as on the MPLS Framework document [1]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-arch-01.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-arch-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-arch-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980407133505.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-arch-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-arch-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980407133505.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Thu Apr 9 11:46:29 1998 Delivery-Date: Thu, 09 Apr 1998 11:58:16 -0400 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.5/8.8.7a) id LAA15992 for ietf-123-outbound.10@ietf.org; Thu, 9 Apr 1998 11:45:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id KAA12729; Thu, 9 Apr 1998 10:14:19 -0400 (EDT) Message-Id: <199804091414.KAA12729@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-bgp4-mpls-00.txt Date: Thu, 09 Apr 1998 10:14:18 -0400 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Carrying Label Information in BGP-4 Author(s) : Y. Rekhter, E. Rosen Filename : draft-ietf-mpls-bgp4-mpls-00.txt Pages : 5 Date : 17-Feb-98 When a pair of Label Switch Routers (LSRs) that maintain BGP peering with each other exchange routes, the LSRs also need to exchange label mapping information for these routes. The exchange is accomplished by piggybacking the label mapping information for a route in the same BGP Update message that is used to exchange the route. This document specifies the way in which this is done. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-bgp4-mpls-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-bgp4-mpls-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-bgp4-mpls-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980408165704.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-bgp4-mpls-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-bgp4-mpls-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980408165704.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-ppp@merit.edu Tue Apr 14 23:40:17 1998 Delivery-Date: Tue, 14 Apr 1998 23:40:22 -0400 Return-Path: owner-ietf-ppp@merit.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id XAA15802 for ; Tue, 14 Apr 1998 23:40:06 -0400 (EDT) Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id XAA10590 for ; Tue, 14 Apr 1998 23:42:36 -0400 (EDT) Received: from localhost (daemon@localhost) by merit.edu (8.8.7/8.8.5) with SMTP id XAA27426; Tue, 14 Apr 1998 23:19:03 -0400 (EDT) Received: by merit.edu (bulk_mailer v1.5); Tue, 14 Apr 1998 23:18:35 -0400 Received: (from majordom@localhost) by merit.edu (8.8.7/8.8.5) id XAA27407 for ietf-ppp-outgoing; Tue, 14 Apr 1998 23:18:34 -0400 (EDT) Received: from manaslu.mos.com.np (root@manaslu.mos.com.np [202.52.255.3]) by merit.edu (8.8.7/8.8.5) with SMTP id XAA27403 for ; Tue, 14 Apr 1998 23:18:24 -0400 (EDT) Received: from kopila.mos.com.np (kopila.mos.com.np [202.52.255.20]) by manaslu.mos.com.np (8.6.9/8.6.9) with ESMTP id JAA18112; Wed, 15 Apr 1998 09:01:46 +0545 Received: (from badri@localhost) by kopila.mos.com.np (8.8.5/KRG1.0) id JAA12450; Wed, 15 Apr 1998 09:33:06 +0545 (NPT) Date: Wed, 15 Apr 1998 09:33:03 +0545 (NPT) From: Badri Ghimire To: Naganand Doraswamy cc: ipsec@tis.com, mpls@external.cisco.com, ietf-ppp@merit.edu, int-serv@ISI.EDU Subject: Re: VPN mailing list In-Reply-To: <3.0.32.19980208105656.00b7bb68@bl-mail1.corpeast.baynetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-ppp@merit.edu Hi, I'm trying to implement VPDN( Virtual Private Dialup Network) with Cisco routers and having a hard time. Can anyone point me to a right resources ( Mailing list, URL etc ) for it, mailing list would be the best. Any pointer on this would be highly appreciated. Thanks. From owner-ietf-ppp@merit.edu Wed Apr 15 14:19:46 1998 Delivery-Date: Wed, 15 Apr 1998 14:19:46 -0400 Return-Path: owner-ietf-ppp@merit.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id OAA07525 for ; Wed, 15 Apr 1998 14:19:45 -0400 (EDT) Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id OAA12918 for ; Wed, 15 Apr 1998 14:22:13 -0400 (EDT) Received: from localhost (daemon@localhost) by merit.edu (8.8.7/8.8.5) with SMTP id NAA08333; Wed, 15 Apr 1998 13:59:03 -0400 (EDT) Received: by merit.edu (bulk_mailer v1.5); Wed, 15 Apr 1998 13:53:53 -0400 Received: (from majordom@localhost) by merit.edu (8.8.7/8.8.5) id NAA08228 for ietf-ppp-outgoing; Wed, 15 Apr 1998 13:53:52 -0400 (EDT) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by merit.edu (8.8.7/8.8.5) with ESMTP id NAA08224 for ; Wed, 15 Apr 1998 13:53:47 -0400 (EDT) Received: from boonmark-pc.juniper.net (boonmark-pc.juniper.net [208.197.169.204]) by red.juniper.net (8.8.5/8.8.5) with ESMTP id KAA10932; Wed, 15 Apr 1998 10:52:41 -0700 (PDT) Received: (from boonmark@localhost) by boonmark-pc.juniper.net (8.8.7/8.7.3) id SAA17799; Wed, 15 Apr 1998 18:52:40 +0100 (BST) Date: Wed, 15 Apr 98 18:52:40 WET DST From: Pasvorn Boonmark To: Badri Ghimire Cc: Naganand Doraswamy , ipsec@tis.com, mpls@external.cisco.com, ietf-ppp@merit.edu, int-serv@isi.edu Subject: Re: VPN mailing list In-Reply-To: Your message of Wed, 15 Apr 1998 09:33:03 +0545 (NPT) Message-ID: Sender: owner-ietf-ppp@merit.edu > > Hi, > > I'm trying to implement VPDN( Virtual Private Dialup Network) with Cisco > routers and having a hard time. Can anyone point me to a right resources > ( Mailing list, URL etc ) for it, mailing list would be the best. Any > pointer on this would be highly appreciated. > > Thanks. > > > > Have you looked at the cco.cisco.com? You can send e-mail to "tac@cisco.com" to request for a case, or alternatively send e-mail to Cisco users mailing list "cisco@spot.colorado.edu" From adm Tue Jun 30 11:26:48 1998 Delivery-Date: Tue, 30 Jun 1998 11:44:18 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id LAA17051 for ietf-123-outbound.10@ietf.org; Tue, 30 Jun 1998 11:25:01 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA14121; Tue, 30 Jun 1998 09:36:46 -0400 (EDT) Message-Id: <199806301336.JAA14121@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-git-uus-00.txt Date: Tue, 30 Jun 1998 09:36:45 -0400 Sender: cclark@ns.cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol Author(s) : M. Suzuki Filename : draft-ietf-mpls-git-uus-00.txt Pages : 25 Date : 29-Jun-98 The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. The assignment, that is specified in section 4 of this document, is designed for advanced B-ISDN signaling support of the Internet protocol, especially the B-ISDN signaling support for the connection that corresponds to the session in the Internet protocol which is clarified in section 2. This specification provides an indispensable framework for the implementation of long-lived session and QoS- sensitive session transfers over ATM. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-git-uus-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-git-uus-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-git-uus-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980629132747.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-git-uus-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-git-uus-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980629132747.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ion@sunroof.Eng.Sun.COM Wed Jul 1 21:49:17 1998 Delivery-Date: Wed, 01 Jul 1998 21:49:18 -0400 Return-Path: owner-ion@sunroof.Eng.Sun.COM Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.8.5/8.8.7a) with SMTP id VAA19061 for ; Wed, 1 Jul 1998 21:49:17 -0400 (EDT) Received: from Eng.Sun.COM (engmail4 [129.144.134.6]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id SAA16900; Wed, 1 Jul 1998 18:43:21 -0700 Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id SAA24758; Wed, 1 Jul 1998 18:43:19 -0700 Received: by sunroof.eng.sun.com (8.9.1.Beta1+Sun/8.9.1.Beta1) id SAA03580 for ion-dist; Wed, 1 Jul 1998 18:36:30 -0700 (PDT) Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.9.1.Beta1+Sun/8.9.1.Beta1) with SMTP id SAA03573 for ; Wed, 1 Jul 1998 18:36:17 -0700 (PDT) Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id SAA19198 for ; Wed, 1 Jul 1998 18:36:17 -0700 Received: from infer.nal.ecl.net (infer.nal.ecl.net [163.138.70.32]) by earth.sun.com (8.8.8/8.8.8) with SMTP id SAA06268 for ; Wed, 1 Jul 1998 18:36:16 -0700 (PDT) Received: by infer.nal.ecl.net (4.1/eclnet*nal.mx4) with TCP; Thu, 2 Jul 98 10:31:17 JST Message-Id: <9807020131.AA14299@infer.nal.ecl.net> To: mpls@external.cisco.com Cc: ion@sunroof.Eng.Sun.COM Subject: (ION) Internet-Drafts@ietf.org: I-D ACTION:draft-ietf-mpls-git-uus-00.txt Date: Thu, 02 Jul 1998 10:31:17 +0900 From: Muneyoshi Suzuki Sender: owner-ion@sunroof.Eng.Sun.COM Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to ion@sunroof.eng.sun.com X-Info: Hypermail archive at http://netlab.ucs.indiana.edu/hypermail/ion/ Dear, I'm writing to inform you that in the ITU-T SG11 Geneva meeting held in May 1998, WP1 decided to enhance the Q.2941 Generic Identifier Transport for the Internet Protocol, especially MPLS VCID support. and WP1 developed the Awaiting-review text (initial draft). WP1 also decided to continue discussion on the User-to-user signaling support for the Internet protocol. I submitted the following Internet Draft which reflects discussion in the last IETF and SG11 meetings. This draft is *much* different from the previous version. Q.2942.2 Awaiting-review text may be frozen in the SG11 Brussels meeting which will be held in November 1998. So, if you have comments, suggestions, or questions to the draft, please let me know ASAP. Best Regards, Muneyoshi Suzuki NTT Multimedia Net. Labs. ------- Forwarded Message Message-Id: <199806301336.JAA14121@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: ;@IETF-Announce.nal.ecl.net Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-git-uus-00.txt Date: Tue, 30 Jun 1998 09:36:45 -0400 Sender: cclark@ns.cnri.reston.va.us - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol Author(s) : M. Suzuki Filename : draft-ietf-mpls-git-uus-00.txt Pages : 25 Date : 29-Jun-98 The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. The assignment, that is specified in section 4 of this document, is designed for advanced B-ISDN signaling support of the Internet protocol, especially the B-ISDN signaling support for the connection that corresponds to the session in the Internet protocol which is clarified in section 2. This specification provides an indispensable framework for the implementation of long-lived session and QoS- sensitive session transfers over ATM. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-git-uus-00.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-git-uus-00.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-git-uus-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980629132747.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-git-uus-00.txt - --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-git-uus-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980629132747.I-D@ietf.org> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe ion' in the body of the message. From adm Tue Jul 14 09:29:15 1998 Delivery-Date: Tue, 14 Jul 1998 09:40:27 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id JAA28516 for ietf-123-outbound.10@ietf.org; Tue, 14 Jul 1998 09:25:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA25404; Tue, 14 Jul 1998 07:53:37 -0400 (EDT) Message-Id: <199807141153.HAA25404@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-arch-02.txt Date: Tue, 14 Jul 1998 07:53:37 -0400 Sender: scoya@ns.cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Multiprotocol Label Switching Architecture Author(s) : E. Rosen, A. Viswanathan, R. Callon Filename : draft-ietf-mpls-arch-02.txt Pages : 64 Date : 13-Jul-98 This internet draft specifies the architecture for multiprotocol label switching (MPLS). The architecture is based on other label switching approaches [2-11] as well as on the MPLS Framework document [1]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-arch-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-arch-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-arch-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980713102139.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-arch-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-arch-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980713102139.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Tue Jul 14 09:39:11 1998 Delivery-Date: Tue, 14 Jul 1998 09:52:33 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id JAA28880 for ietf-123-outbound.10@ietf.org; Tue, 14 Jul 1998 09:35:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA25418; Tue, 14 Jul 1998 07:53:44 -0400 (EDT) Message-Id: <199807141153.HAA25418@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mpls@external.cisco.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-mpls-label-encaps-02.txt Date: Tue, 14 Jul 1998 07:53:43 -0400 Sender: scoya@ns.cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : MPLS Label Stack Encoding Author(s) : E. Rosen, Y. Rekhter, D. Tappan, D. Farinacci, G. Fedorkow, T. Li, A. Conta Filename : draft-ietf-mpls-label-encaps-02.txt Pages : 21 Date : 13-Jul-98 "Multi-Protocol Label Switching (MPLS)" [1,2,3] requires a set of procedures for augmenting network layer packets with "label stacks", thereby turning them into "labeled packets". Routers which support MPLS are known as "Label Switching Routers", or "LSRs". In order to transmit a labeled packet on a particular data link, an LSR must support an encoding technique which, given a label stack and a network layer packet, produces a labeled packet. This document specifies the encoding to be used by an LSR in order to transmit labeled packets on PPP data links and possibly on other data links as well. On some data links, the label at the top of the stack may be encoded in a different manner, but the techniques described here MUST be used to encode the remainder of the label stack. This document also specifies rules and procedures for processing the various fields of the label stack encoding. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-label-encaps-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-mpls-label-encaps-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-label-encaps-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980713102523.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-label-encaps-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-label-encaps-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980713102523.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-qosr@ca.newbridge.com Wed Jul 15 18:38:03 1998 Delivery-Date: Wed, 15 Jul 1998 18:38:08 -0400 Return-Path: owner-qosr@ca.newbridge.com Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA27398 for ; Wed, 15 Jul 1998 18:38:03 -0400 (EDT) Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id SAA25626; Wed, 15 Jul 1998 18:30:20 -0400 (EDT) Received: from kanata-gw1.newbridge.com(192.75.23.72), claiming to be "kanata-gw1.ca.newbridge.com" via SMTP by ns.newbridge.com, id smtpdAAAa25432; Wed Jul 15 18:29:59 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 15 Jul 1998 22:29:56 UT Received: from distmaster.newbridge.com (distmaster.ca.newbridge.com [138.120.118.27]) by ca.newbridge.com. (8.8.8/8.8.6) with SMTP id SAA05393; Wed, 15 Jul 1998 18:29:55 -0400 (EDT) Received: by distmaster.newbridge.com (SMI-8.6/SMI-SVR4) id SAA21963; Wed, 15 Jul 1998 18:14:02 -0400 From: gratta@holta.ho.lucent.com To: ion@sunroof.eng.sun.com, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@isi.edu, qosr@newbridge.com, rsvp@isi.edu, rap@iphighway.com Cc: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH Message-Id: <199807152116.RAA24401@holta.ho.lucent.com> Comments: Authenticated sender is Original-To: ion@sunroof.eng.sun.com, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@isi.edu, qosr@newbridge.com, rsvp@isi.edu, rap@iphighway.com Date: Wed, 15 Jul 1998 17:26:40 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: ITU-T SG 11 discussions concerning Internet interoperation with Original-CC: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH X-mailer: Pegasus Mail for Windows (v2.52) Sender: owner-qosr@ca.newbridge.com Precedence: bulk X-Info: [Un]Subscribe to qosr-request@newbridge.com ITU-Telecommunication Standardization Sector Study Group 11 Questions: ALL (SoI) SUBJECT: Status of SoI discussions concerning Internet interoperation with DSS2 and B-ISUP signalling APPROVAL: ITU-T SG 11 in Geneva, 22 May 1998 1. Introduction The May 1998 meeting of ITU-T SG 11 benefited from the participation of the following ISOC representatives: - Dr. Hui-Lan Lu, ISOC representative appointed by the PSTN/Internet Internetworking Working Group to Working Party 4/11 (Intelligent Networks)(Questions 5/11 and 22/11); - Mr. Joel M. Halpern, ISOC representative at ITU-T Study Group 11 Meeting, Geneva, 4-15 May 1998; and - Mr. Matt Holdrege, IETF Transport Directorate Liaison to ITU-T SG 11. Their contributions to the progress of our work during our May 1998 meeting were significant both in technical substance and in assisting the participants of ITU-T SG 11 to understand the ongoing work at ISOC/IETF, thus initiating a constructive dialogue between the two organizations. 2. Future interactions ITU-T SG 11 has appointed Dr. Kenichi KITAMI, Chairman of Working Party 1/11, to serve as overall point of contact with the ISOC/IETF. His e-mail address is: kitami@magnet.netlab.ntt.co.jp. As the need arises for extensive interaction in particular work areas, it is our intention to appoint appropriate individuals as contact persons in those areas, so that distributed communications may accelerate information exchange. So far the following points of contact have been identified: Subject: DSS2 and B-ISUP support of services over the Internet IETF Working Groups: ION, MPLS, DIFF-SERV, INT-SERV, RSVP, RAP Contact: Dr. Kenichi KITAMI, kitami@magnet.netlab.ntt.co.jp Subject: Intelligent Network interoperation with services over the Internet IETF Working Groups: PINT Contact: Professor Zhengkun Mi, mizk@njupt.edu.cn 3. Major Achievements of the ITU-T SG11 May 1998 meeting 3.1 Major objectives of ITU-T SG 11 concerning Signalling Support of Services Over the Internet The participants agreed that there are 5 objectives for efforts within Study Group 11 for standardization of Signalling Support of Services Over the Internet (SoI): a) Efficiently identifying and routing traffic destined for Internet Service Providers (ISPs) to minimize negative impact upon the Public Switched Telephone Network (PSTN), which has been engineered for relatively short holding time calls; b) Defining signalling support for new, value added services which may enable public network operators, as well as ISPs, to capitalize on the growing demand for Internet based and Intelligent Network (IN) based capabilities; c) Serving the need of ISPs, Internet Access Providers, and "Internet users" to flexibly manage dynamic bandwidth and quality of service demands from a public network; d) Defining mobile wireless access to services over the Internet, e.g., virtual private networks, provided by either ISPs or public network operators; and e) Signalling support for Service Interworking of both dialup Internet access data applications and Voice over IP applications with traditional telecommunication services, including support of signalling applications and user parts over IP based networks. 3.2 DSS2 and B-ISUP support of services over the Internet Related to objective c) mentioned above, ITU-T SG 11 received a written indication from the co- chairman of the MPLS WG that support for the end to end transport of MPLS VCID had been discussed in the MPLS WG and were considering the use of a structured UUI information element. A number of contributions addressing this subject were also received. The result of the discussions within ITU-T SG 11 are: 1) Agreement to associate an ATM Virtual Connection with an Internet Session, or an MPLS VCID, at the occasion of the connection setup, via the Generic Identifier Transport information element; 2) The creation of two baseline documents, one for DSS2 (UNI signalling)and the other for B- ISUP (NNI signalling); and 3) Agreement in principle to initiate approval of the draft Recommendation in the next ITU-T SG 11 meeting in March 1999 (implying final approval in February 2000). Individuals interested in viewing the details of the DSS2 baseline document should send a request to gratta@lucent.com. A Word format document (of TD GEN/11-67R1) will be forwarded to such individuals. Greg Ratta, Vice Chairman, ITU-T WP 1/11 Lucent Technologies Tel: +1 732 332 5174, Fax: +1 732 949 1196, gratta@lucent.com From owner-diff-serv@BayNetworks.COM Wed Jul 15 18:42:41 1998 Delivery-Date: Wed, 15 Jul 1998 18:42:42 -0400 Return-Path: owner-diff-serv@BayNetworks.COM Received: from smtp-gw.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA27492 for ; Wed, 15 Jul 1998 18:42:41 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA28157; Wed, 15 Jul 1998 18:35:52 -0400 (EDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA27680; Wed, 15 Jul 1998 18:33:51 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id SAA03931; Wed, 15 Jul 1998 18:23:11 -0400 (EDT) for diff-serv-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-diff-serv@majordomo using -f Received: from mailhost.BayNetworks.COM (h016d.s86b1.BayNetworks.COM [134.177.1.109] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id SAA03927; Wed, 15 Jul 1998 18:22:29 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id PAA21443 for ; Wed, 15 Jul 1998 15:13:31 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id SAA03923; Wed, 15 Jul 1998 18:21:56 -0400 (EDT) for Received: from ihgw2.lucent.com (ihgw2.lucent.com [207.19.48.2]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with SMTP id SAA27562 for ; Wed, 15 Jul 1998 18:13:32 -0400 (EDT) From: gratta@holta.ho.lucent.com To: ion@sunroof.eng.sun.com, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@ISI.EDU, qosr@newbridge.com, rsvp@ISI.EDU, rap@iphighway.com Cc: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH Received: from holta.ho.lucent.com by ihig2.firewall.lucent.com (SMI-8.6/EMS-L sol2) id RAA26181; Wed, 15 Jul 1998 17:02:12 -0500 Received: from nj7460grattal.holta by holta.ho.lucent.com (SMI-8.6/EMS-1.4.1 sol2) id RAA24401; Wed, 15 Jul 1998 17:16:24 -0400 Message-Id: <199807152116.RAA24401@holta.ho.lucent.com> Comments: Authenticated sender is Original-To: ion@sunroof.eng.sun.com, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@isi.edu, qosr@newbridge.com, rsvp@isi.edu, rap@iphighway.com Date: Wed, 15 Jul 1998 17:26:40 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: ITU-T SG 11 discussions concerning Internet interoperation with Original-CC: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH X-mailer: Pegasus Mail for Windows (v2.52) Sender: owner-diff-serv@BayNetworks.COM Precedence: bulk ITU-Telecommunication Standardization Sector Study Group 11 Questions: ALL (SoI) SUBJECT: Status of SoI discussions concerning Internet interoperation with DSS2 and B-ISUP signalling APPROVAL: ITU-T SG 11 in Geneva, 22 May 1998 1. Introduction The May 1998 meeting of ITU-T SG 11 benefited from the participation of the following ISOC representatives: - Dr. Hui-Lan Lu, ISOC representative appointed by the PSTN/Internet Internetworking Working Group to Working Party 4/11 (Intelligent Networks)(Questions 5/11 and 22/11); - Mr. Joel M. Halpern, ISOC representative at ITU-T Study Group 11 Meeting, Geneva, 4-15 May 1998; and - Mr. Matt Holdrege, IETF Transport Directorate Liaison to ITU-T SG 11. Their contributions to the progress of our work during our May 1998 meeting were significant both in technical substance and in assisting the participants of ITU-T SG 11 to understand the ongoing work at ISOC/IETF, thus initiating a constructive dialogue between the two organizations. 2. Future interactions ITU-T SG 11 has appointed Dr. Kenichi KITAMI, Chairman of Working Party 1/11, to serve as overall point of contact with the ISOC/IETF. His e-mail address is: kitami@magnet.netlab.ntt.co.jp. As the need arises for extensive interaction in particular work areas, it is our intention to appoint appropriate individuals as contact persons in those areas, so that distributed communications may accelerate information exchange. So far the following points of contact have been identified: Subject: DSS2 and B-ISUP support of services over the Internet IETF Working Groups: ION, MPLS, DIFF-SERV, INT-SERV, RSVP, RAP Contact: Dr. Kenichi KITAMI, kitami@magnet.netlab.ntt.co.jp Subject: Intelligent Network interoperation with services over the Internet IETF Working Groups: PINT Contact: Professor Zhengkun Mi, mizk@njupt.edu.cn 3. Major Achievements of the ITU-T SG11 May 1998 meeting 3.1 Major objectives of ITU-T SG 11 concerning Signalling Support of Services Over the Internet The participants agreed that there are 5 objectives for efforts within Study Group 11 for standardization of Signalling Support of Services Over the Internet (SoI): a) Efficiently identifying and routing traffic destined for Internet Service Providers (ISPs) to minimize negative impact upon the Public Switched Telephone Network (PSTN), which has been engineered for relatively short holding time calls; b) Defining signalling support for new, value added services which may enable public network operators, as well as ISPs, to capitalize on the growing demand for Internet based and Intelligent Network (IN) based capabilities; c) Serving the need of ISPs, Internet Access Providers, and "Internet users" to flexibly manage dynamic bandwidth and quality of service demands from a public network; d) Defining mobile wireless access to services over the Internet, e.g., virtual private networks, provided by either ISPs or public network operators; and e) Signalling support for Service Interworking of both dialup Internet access data applications and Voice over IP applications with traditional telecommunication services, including support of signalling applications and user parts over IP based networks. 3.2 DSS2 and B-ISUP support of services over the Internet Related to objective c) mentioned above, ITU-T SG 11 received a written indication from the co- chairman of the MPLS WG that support for the end to end transport of MPLS VCID had been discussed in the MPLS WG and were considering the use of a structured UUI information element. A number of contributions addressing this subject were also received. The result of the discussions within ITU-T SG 11 are: 1) Agreement to associate an ATM Virtual Connection with an Internet Session, or an MPLS VCID, at the occasion of the connection setup, via the Generic Identifier Transport information element; 2) The creation of two baseline documents, one for DSS2 (UNI signalling)and the other for B- ISUP (NNI signalling); and 3) Agreement in principle to initiate approval of the draft Recommendation in the next ITU-T SG 11 meeting in March 1999 (implying final approval in February 2000). Individuals interested in viewing the details of the DSS2 baseline document should send a request to gratta@lucent.com. A Word format document (of TD GEN/11-67R1) will be forwarded to such individuals. Greg Ratta, Vice Chairman, ITU-T WP 1/11 Lucent Technologies Tel: +1 732 332 5174, Fax: +1 732 949 1196, gratta@lucent.com From owner-ion@sunroof.Eng.Sun.COM Wed Jul 15 18:43:44 1998 Delivery-Date: Wed, 15 Jul 1998 18:43:45 -0400 Return-Path: owner-ion@sunroof.Eng.Sun.COM Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.8.5/8.8.7a) with SMTP id SAA27509 for ; Wed, 15 Jul 1998 18:43:43 -0400 (EDT) Received: from Eng.Sun.COM (engmail4 [129.144.134.6]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id PAA01529; Wed, 15 Jul 1998 15:31:52 -0700 Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id PAA08293; Wed, 15 Jul 1998 15:31:50 -0700 Received: by sunroof.eng.sun.com (8.9.1+Sun/8.9.1) id PAA06258 for ion-dist; Wed, 15 Jul 1998 15:23:52 -0700 (PDT) Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.9.1+Sun/8.9.1) with SMTP id PAA06251 for ; Wed, 15 Jul 1998 15:23:43 -0700 (PDT) From: gratta@holta.ho.lucent.com Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id PAA10862 for ; Wed, 15 Jul 1998 15:23:38 -0700 Received: from ihgw2.lucent.com (ihgw2.lucent.com [207.19.48.2]) by earth.sun.com (8.8.8/8.8.8) with SMTP id PAA08376 for ; Wed, 15 Jul 1998 15:23:31 -0700 (PDT) To: ion@sunroof.Eng.Sun.COM, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@isi.edu, qosr@newbridge.com, rsvp@isi.edu, rap@iphighway.com Cc: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH Received: from holta.ho.lucent.com by ihig2.firewall.lucent.com (SMI-8.6/EMS-L sol2) id RAA26181; Wed, 15 Jul 1998 17:02:12 -0500 Received: from nj7460grattal.holta by holta.ho.lucent.com (SMI-8.6/EMS-1.4.1 sol2) id RAA24401; Wed, 15 Jul 1998 17:16:24 -0400 Message-Id: <199807152116.RAA24401@holta.ho.lucent.com> Comments: Authenticated sender is Original-To: ion@sunroof.eng.sun.com, mpls@external.cisco.com, diff-serv@BayNetworks.COM, int-serv@isi.edu, qosr@newbridge.com, rsvp@isi.edu, rap@iphighway.com Date: Wed, 15 Jul 1998 17:26:40 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: (ION) ITU-T SG 11 discussions concerning Internet interoperation with Original-CC: rcoltun@fore.com, nip-kita@ma.kcom.ne.jp, ARSHEY.ODEDRA@ITU.CH X-mailer: Pegasus Mail for Windows (v2.52) Sender: owner-ion@sunroof.Eng.Sun.COM Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to ion@sunroof.eng.sun.com X-Info: Hypermail archive at http://netlab.ucs.indiana.edu/hypermail/ion/ ITU-Telecommunication Standardization Sector Study Group 11 Questions: ALL (SoI) SUBJECT: Status of SoI discussions concerning Internet interoperation with DSS2 and B-ISUP signalling APPROVAL: ITU-T SG 11 in Geneva, 22 May 1998 1. Introduction The May 1998 meeting of ITU-T SG 11 benefited from the participation of the following ISOC representatives: - Dr. Hui-Lan Lu, ISOC representative appointed by the PSTN/Internet Internetworking Working Group to Working Party 4/11 (Intelligent Networks)(Questions 5/11 and 22/11); - Mr. Joel M. Halpern, ISOC representative at ITU-T Study Group 11 Meeting, Geneva, 4-15 May 1998; and - Mr. Matt Holdrege, IETF Transport Directorate Liaison to ITU-T SG 11. Their contributions to the progress of our work during our May 1998 meeting were significant both in technical substance and in assisting the participants of ITU-T SG 11 to understand the ongoing work at ISOC/IETF, thus initiating a constructive dialogue between the two organizations. 2. Future interactions ITU-T SG 11 has appointed Dr. Kenichi KITAMI, Chairman of Working Party 1/11, to serve as overall point of contact with the ISOC/IETF. His e-mail address is: kitami@magnet.netlab.ntt.co.jp. As the need arises for extensive interaction in particular work areas, it is our intention to appoint appropriate individuals as contact persons in those areas, so that distributed communications may accelerate information exchange. So far the following points of contact have been identified: Subject: DSS2 and B-ISUP support of services over the Internet IETF Working Groups: ION, MPLS, DIFF-SERV, INT-SERV, RSVP, RAP Contact: Dr. Kenichi KITAMI, kitami@magnet.netlab.ntt.co.jp Subject: Intelligent Network interoperation with services over the Internet IETF Working Groups: PINT Contact: Professor Zhengkun Mi, mizk@njupt.edu.cn 3. Major Achievements of the ITU-T SG11 May 1998 meeting 3.1 Major objectives of ITU-T SG 11 concerning Signalling Support of Services Over the Internet The participants agreed that there are 5 objectives for efforts within Study Group 11 for standardization of Signalling Support of Services Over the Internet (SoI): a) Efficiently identifying and routing traffic destined for Internet Service Providers (ISPs) to minimize negative impact upon the Public Switched Telephone Network (PSTN), which has been engineered for relatively short holding time calls; b) Defining signalling support for new, value added services which may enable public network operators, as well as ISPs, to capitalize on the growing demand for Internet based and Intelligent Network (IN) based capabilities; c) Serving the need of ISPs, Internet Access Providers, and "Internet users" to flexibly manage dynamic bandwidth and quality of service demands from a public network; d) Defining mobile wireless access to services over the Internet, e.g., virtual private networks, provided by either ISPs or public network operators; and e) Signalling support for Service Interworking of both dialup Internet access data applications and Voice over IP applications with traditional telecommunication services, including support of signalling applications and user parts over IP based networks. 3.2 DSS2 and B-ISUP support of services over the Internet Related to objective c) mentioned above, ITU-T SG 11 received a written indication from the co- chairman of the MPLS WG that support for the end to end transport of MPLS VCID had been discussed in the MPLS WG and were considering the use of a structured UUI information element. A number of contributions addressing this subject were also received. The result of the discussions within ITU-T SG 11 are: 1) Agreement to associate an ATM Virtual Connection with an Internet Session, or an MPLS VCID, at the occasion of the connection setup, via the Generic Identifier Transport information element; 2) The creation of two baseline documents, one for DSS2 (UNI signalling)and the other for B- ISUP (NNI signalling); and 3) Agreement in principle to initiate approval of the draft Recommendation in the next ITU-T SG 11 meeting in March 1999 (implying final approval in February 2000). Individuals interested in viewing the details of the DSS2 baseline document should send a request to gratta@lucent.com. A Word format document (of TD GEN/11-67R1) will be forwarded to such individuals. Greg Ratta, Vice Chairman, ITU-T WP 1/11 Lucent Technologies Tel: +1 732 332 5174, Fax: +1 732 949 1196, gratta@lucent.com X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe ion' in the body of the message.