Internet Engineering Task Force Fred M. Burg Internet Draft Edward M. Hope Draft-burg-iptel-trip-gw-id-00.txt James M. Amster February 22, 2002 Radhika R. Roy Expires: October 21, 2002 AT&T Gateway Identification for TRIP_GW Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This contribution has proposed that an identification of the gateway needs to be provided. The identification of a gateway is required in many circumstances especially in the VPN environment. Radhika R. Roy [Page 1] Internet Draft TRIP-GW ID February 22, 2002 1. Introduction Currently, the TRIP-GW proposal [2] is being taken as the IPTEL WG work item. In this proposal, it is seen that a new identification is needed. This identification can be termed as the site identification of the gateway. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [3]. 3. Proposal The current Internet Draft for TRIP-GW [2] assumes that a Gateway has full knowledge of the full E.164 numbers and serving carriers for which it provides service. This works well for gateways interfacing to the PSTN, as discussed in 4.1 of [2] and may also work for gateways on customer premise that may be part of a VPN. In the latter case, however, the gateway may only know the last four or so digits of a private numbering plan and not the higher order digits (e.g., country code, etc.). To satisfy the current requirements of TRIP-GW in reporting full E.164 numbers, the gateway would need to have this additional higher-order information (i.e, be able to perform number normilization). There is also a requirement to have the same generic dial-plan on all premise gateways and do number normalization at the location server or controller. That is, gateways need to be able to report a number such as 6789 to a location server, where 6789 from VPN-A is distinguishable from 6789 from VPN-B. As a result, there is a need in TRIP-GW to address the needs of gateways that are part of a VPN environment. One specific need would be to identify the location of the gateway - a Site ID. This is different than the Carrier Identification Code (CIC), which really identifies public carriers and should not be used in the above way. The proposed Site ID is similar to how the H.323 ID is used today. There are other VPN attributes that would be useful to specify in TRIP-GW - some for reporting purposes. Therefore, it is proposed to add an attribute along the lines of other "family attributes" currently specified in TRIP-GW. This could be a "Premise Identification Family". It would have a status of Fred M. Burg, et. al. [Page 2] Internet Draft TRIP-GW ID February 22, 2002 Mandatory: False since, clearly, it would not be used for gateways facing the PSTN. With such an addition, it is believed that the current draft of TRIP-GW should advance as proposed. 4. Conclusion We have shown why a gateway needs to be provided its identification. At present, the TRIP-GW [2] proposal does not have it. We have proposed that a site/gateway identification needs to be added in the proposed draft [2]. Fred M. Burg, et. al. [Page 3] Internet Draft TRIP-GW ID February 22, 2002 4. References [1] Bradner, S., "The Internet Standards Process -- Revision 3," BCP 9, RFC 2026, October 1996. [2] Rosenberg, J., H. Salama, H., Bangalore, M., Shah, D., Kumar, R., _Usage of TRIP in Gateways for Exporting Phone Routes,_ draft- rs-trip-gw-03.txt, IETF, Work in progress. [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels," BCP 14, RFC 2119, March 1997. Acknowledgments TBD Author's Addresses Fred M. Burg AT&T Room C3-2A27 200 S. Laurel Avenue Middletown, NJ 07748, USA Phone: +1 732 420 8849 Fax: + 1 732 368 1617 Email: fburg@att.com Edward M. Hope AT&T Room B5-3D30 200 S. Laurel Avenue Middletown, NJ 07748, USA Phone: +1 732 420 8848 Email: ehope@att.com James M. Amster AT&T Room B5-2A18 200 S. Laurel Avenue Middletown, NJ 07748, USA Phone: +1 732 420 8831 Fax: + 1 732 368 9625 Email: jamster@att.com Radhika R. Roy AT&T Room D3_3C09 Fred M. Burg, et. al. [Page 4] Internet Draft TRIP-GW ID February 22, 2002 200 S. Laurel Avenue Middletown, NJ 07748, USA Phone: +1 732 420 1580 Fax: + 1 732 368 1302 Email: rrroy@att.com Full Copyright Statement This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. Fred M. Burg, et. al. [Page 5]