draft-ietf-nsis-tunnel-00.txt   draft-ietf-nsis-tunnel-01.txt 
IETF Next Steps in Signaling C. Shen IETF Next Steps in Signaling C. Shen
Internet-Draft H. Schulzrinne Internet-Draft H. Schulzrinne
Expires: December 21, 2006 Columbia U. Intended status: Standards Track Columbia U.
S. Lee Expires: April 24, 2007 S. Lee
J. Bang J. Bang
Samsung AIT Samsung AIT
June 19, 2006 October 21, 2006
NSIS Operation Over IP Tunnels NSIS Operation Over IP Tunnels
draft-ietf-nsis-tunnel-00.txt draft-ietf-nsis-tunnel-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 21, 2006. This Internet-Draft will expire on April 24, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This draft presents an NSIS operation over IP tunnel scheme using QoS This draft presents an NSIS operation over IP tunnel scheme using QoS
NSLP as the NSIS signaling application. Both sender-initiated and NSLP as the NSIS signaling application. Both sender-initiated and
receiver-initiated NSIS signaling modes are discussed. The scheme receiver-initiated NSIS signaling modes are discussed. The scheme
skipping to change at page 3, line 17 skipping to change at page 3, line 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 9. Security Considerations . . . . . . . . . . . . . . . . . . . 27
10. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 10. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
10.1. Various Design Alternatives . . . . . . . . . . . . . . . 27 10.1. Various Design Alternatives . . . . . . . . . . . . . . . 27
10.1.1. End-to-end and Tunnel Signaling Interaction Model . . 27 10.1.1. End-to-end and Tunnel Signaling Interaction Model . . 27
10.1.2. Packet Classification over the Tunnel . . . . . . . . 28 10.1.2. Packet Classification over the Tunnel . . . . . . . . 28
10.1.3. Tunnel Binding Methods . . . . . . . . . . . . . . . . 28 10.1.3. Tunnel Binding Methods . . . . . . . . . . . . . . . . 28
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.1. Normative References . . . . . . . . . . . . . . . . . . . 29 12.1. Normative References . . . . . . . . . . . . . . . . . . . 29
12.2. Informative References . . . . . . . . . . . . . . . . . . 30 12.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
Intellectual Property and Copyright Statements . . . . . . . . . . 33 Intellectual Property and Copyright Statements . . . . . . . . . . 33
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [1]. document are to be interpreted as described in [1].
2. Introduction 2. Introduction
skipping to change at page 30, line 8 skipping to change at page 30, line 8
11. Acknowledgements 11. Acknowledgements
12. References 12. References
12.1. Normative References 12.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Schulzrinne, H. and R. Hancock, "GIST: General Internet [2] Schulzrinne, H. and R. Hancock, "GIST: General Internet
Signaling Transport", draft-ietf-nsis-ntlp-09 (work in Signaling Transport", draft-ietf-nsis-ntlp-11 (work in
progress), February 2006. progress), August 2006.
[3] Manner, J., "NSLP for Quality-of-Service Signaling", [3] Manner, J., "NSLP for Quality-of-Service Signaling",
draft-ietf-nsis-qos-nslp-10 (work in progress), March 2006. draft-ietf-nsis-qos-nslp-11 (work in progress), June 2006.
12.2. Informative References 12.2. Informative References
[4] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic [4] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation (GRE)", RFC 1701, October 1994. Routing Encapsulation (GRE)", RFC 1701, October 1994.
[5] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic [5] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation over IPv4 networks", RFC 1702, Routing Encapsulation over IPv4 networks", RFC 1702,
October 1994. October 1994.
skipping to change at page 30, line 41 skipping to change at page 30, line 41
[9] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms for [9] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms for
IPv6 Hosts and Routers", RFC 4213, October 2005. IPv6 Hosts and Routers", RFC 4213, October 2005.
[10] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, [10] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303,
December 2005. December 2005.
[11] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 [11] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6
Specification", RFC 2473, December 1998. Specification", RFC 2473, December 1998.
[12] Ash, J., "QoS-NSLP QSPEC Template", draft-ietf-nsis-qspec-09 [12] Ash, J., "QoS NSLP QSPEC Template", draft-ietf-nsis-qspec-12
(work in progress), March 2006. (work in progress), October 2006.
[13] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol [13] Stiemerling, M., "NAT/Firewall NSIS Signaling Layer Protocol
(NSLP)", draft-ietf-nsis-nslp-natfw-11 (work in progress), (NSLP)", draft-ietf-nsis-nslp-natfw-12 (work in progress),
April 2006. June 2006.
[14] Lee, S., "Applicability Statement of NSIS Protocols in Mobile [14] Lee, S., "Applicability Statement of NSIS Protocols in Mobile
Environments", Environments",
draft-ietf-nsis-applicability-mobility-signaling-04 (work in draft-ietf-nsis-applicability-mobility-signaling-05 (work in
progress), March 2006. progress), June 2006.
[15] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, [15] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina,
"Generic Routing Encapsulation (GRE)", RFC 2784, March 2000. "Generic Routing Encapsulation (GRE)", RFC 2784, March 2000.
[16] Terzis, A., Krawczyk, J., Wroclawski, J., and L. Zhang, "RSVP [16] Terzis, A., Krawczyk, J., Wroclawski, J., and L. Zhang, "RSVP
Operation Over IP Tunnels", RFC 2746, January 2000. Operation Over IP Tunnels", RFC 2746, January 2000.
[17] Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC Data [17] Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC Data
Flows", RFC 2207, September 1997. Flows", RFC 2207, September 1997.
skipping to change at page 32, line 35 skipping to change at page 32, line 4
Email: schulzrinne@cs.columbia.edu Email: schulzrinne@cs.columbia.edu
Sung-Hyuck Lee Sung-Hyuck Lee
SAMSUNG Advanced Institute of Technology SAMSUNG Advanced Institute of Technology
San 14-1, Nongseo-ri, Giheung-eup San 14-1, Nongseo-ri, Giheung-eup
Yongin-si, Gyeonggi-do 449-712 Yongin-si, Gyeonggi-do 449-712
KOREA KOREA
Phone: +82 31 280 9552 Phone: +82 31 280 9552
Email: starsu.lee@samsung.com Email: starsu.lee@samsung.com
Jong Ho Bang Jong Ho Bang
SAMSUNG Advanced Institute of Technology SAMSUNG Advanced Institute of Technology
San 14-1, Nongseo-ri, Giheung-eup San 14-1, Nongseo-ri, Giheung-eup
Yongin-si, Gyeonggi-do 449-712 Yongin-si, Gyeonggi-do 449-712
KOREA KOREA
Phone: +82 31 280 9585 Phone: +82 31 280 9585
Email: jh0278.bang@samsung.com Email: jh0278.bang@samsung.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 33, line 29 skipping to change at page 33, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 14 change blocks. 
33 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/