draft-ietf-iptel-tgrep-03.txt   draft-ietf-iptel-tgrep-04.txt 
IPTEL Working Group Manjunath Bangalore, Cisco Systems IPTEL Working Group Manjunath Bangalore, Cisco Systems
Internet Draft Rajneesh Kumar, Cisco Systems Internet Draft Rajneesh Kumar, Cisco Systems
draft-ietf-iptel-tgrep-03.txt Jonathan Rosenberg, dynamicsoft draft-ietf-iptel-tgrep-04.txt Jonathan Rosenberg, dynamicsoft
March 2004 Hussein Salama, Cisco Systems October 21, 2004 Hussein Salama, Cisco Systems
Expiration Date: September 2004 Dhaval N. Shah, Cisco Systems Expiration Date: April 21, 2005 Dhaval N. Shah, Cisco Systems
A Telephony Gateway REgistration Protocol (TGREP) A Telephony Gateway REgistration Protocol (TGREP)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 April 21, 2005.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document describes the Telephony Gateway Registration Protocol This document describes the Telephony Gateway Registration Protocol
(TGREP) for registration of telephony prefixes supported by telephony (TGREP) for registration of telephony prefixes supported by telephony
gateways and soft switches. The registration mechanism can also be gateways and soft switches. The registration mechanism can also be
used to export resource information. The prefix and resource used to export resource information. The prefix and resource
information can then be passed on to a TRIP Location Server, which in information can then be passed on to a TRIP Location Server, which in
turn can propogate that routing information within and between turn can propogate that routing information within and between
internet telephony administrative domains (ITAD). TGREP shares a lot internet telephony administrative domains (ITAD). TGREP shares a lot
of similarites with the TRIP Protocol. It has similar procedures and of similarites with the TRIP Protocol. It has similar procedures and
skipping to change at page 23, line 29 skipping to change at page 23, line 29
- The Attribute Type Codes for the new attributes: - The Attribute Type Codes for the new attributes:
AvailableCircuits, TotalCircuitCapacity, CallSuccess, Prefix, AvailableCircuits, TotalCircuitCapacity, CallSuccess, Prefix,
TrunkGroup and Carrier described in Sections 3.1, 3.2, 3.3, 3.4, TrunkGroup and Carrier described in Sections 3.1, 3.2, 3.3, 3.4,
3.5 and 3.6 above, respectively, are to be assigned by IANA. 3.5 and 3.6 above, respectively, are to be assigned by IANA.
- The Address Family Codes for the new address families: TrunkGroup - The Address Family Codes for the new address families: TrunkGroup
and Carrier described in Section 3.7, are to be assigned by IANA. and Carrier described in Section 3.7, are to be assigned by IANA.
Both TRIP[4] and TGREP share the same IANA registry for Capabilities, Both TRIP[4] and TGREP share the same IANA registry for Capabilities,
Attributes, Address Families, and Application Protocols Attributes, Address Families, and Application Protocols
6. Changes since draft-ietf-iptel-tgrep-02.txt 6. Changes since draft-ietf-iptel-tgrep-03.txt
- No change in content. Releasing a new revision for renewal of - No change in content. Releasing a new revision for renewal of
draft draft
7. Changes since draft-ietf-iptel-tgrep-01.txt 7. Changes since draft-ietf-iptel-tgrep-02.txt
- No change in content. Releasing a new revision for renewal of
draft
8. Changes since draft-ietf-iptel-tgrep-01.txt
- Added a "Security Considerations" Section to the document - Added a "Security Considerations" Section to the document
- Strengthened the text under "LS/Proxy Behavior" regarding - Strengthened the text under "LS/Proxy Behavior" regarding
Consolidation and Aggregation with additional examples for better Consolidation and Aggregation with additional examples for better
clarity clarity
- Removed the section "Other Attributes" including its subsection - Removed the section "Other Attributes" including its subsection
on the "Pricing" attribute on the "Pricing" attribute
- Modified the definition of Carrier in the "Carrier attribute" and - Modified the definition of Carrier in the "Carrier attribute" and
"TrunkGroup and Carrier Address Families" sections respectively "TrunkGroup and Carrier Address Families" sections respectively
- Rectified the section number references in the "IANA - Rectified the section number references in the "IANA
Considerations" Section Considerations" Section
- Strengthened the text in the attribute sections regarding - Strengthened the text in the attribute sections regarding
dissemination of attributes received on TGREP dissemination of attributes received on TGREP
- Updated the "References" section - Updated the "References" section
- Corrected typos, nits, grammatical errors, and language of the - Corrected typos, nits, grammatical errors, and language of the
text throughout the document based on feedback from the iptel text throughout the document based on feedback from the iptel
community community
8. Changes since draft-ietf-iptel-tgrep-00.txt 9. Changes since draft-ietf-iptel-tgrep-00.txt
- Added recommendations for AvailableCircuits and CallSuccess - Added recommendations for AvailableCircuits and CallSuccess
attributes. attributes.
- Updated Carrier Attribute with ASCII syntax. - Updated Carrier Attribute with ASCII syntax.
- Removed thresholding scheme description. - Removed thresholding scheme description.
- Updated author addresses. - Updated author addresses.
9. Changes since draft-ietf-iptel-trip-gw-00.txt 10. Changes since draft-ietf-iptel-trip-gw-00.txt
- Changed title of the document to TGREP (Telephony Gateway - Changed title of the document to TGREP (Telephony Gateway
REgistration Protocol) REgistration Protocol)
- Changed name of protocol described in this document to TGREP - Changed name of protocol described in this document to TGREP
- Changed Abstract and Introduction sections to position TGREP as - Changed Abstract and Introduction sections to position TGREP as
an auxiliary protocol to TRIP (as opposed to a "subset" of TRIP) an auxiliary protocol to TRIP (as opposed to a "subset" of TRIP)
- Modified the section on LS/Proxy Behavior including the diagram - Modified the section on LS/Proxy Behavior including the diagram
- Added an additional example to the Route Consolidation section - Added an additional example to the Route Consolidation section
- Changed the format of Carrier (both as an attribute and as an AF) - Changed the format of Carrier (both as an attribute and as an AF)
to accomodate representation of Country codes in association with to accomodate representation of Country codes in association with
CICs. CICs.
- Updated text to allow Carrier attribute in TrunkGroup address - Updated text to allow Carrier attribute in TrunkGroup address
family and TrunkGroup attribute in Carrier address family. family and TrunkGroup attribute in Carrier address family.
10. Changes since -03 11. Changes since -03
- Removed Carrier-Trunkgroup attribute and address family and - Removed Carrier-Trunkgroup attribute and address family and
references to it. references to it.
- Added Terminology and Definitions section. - Added Terminology and Definitions section.
- Updated CallSuccess attribute. - Updated CallSuccess attribute.
- Added Prefix attribute. - Added Prefix attribute.
- Added Carrier attribute. - Added Carrier attribute.
- Added TrunkGroup attribute. - Added TrunkGroup attribute.
- Added TrunkGroup Address Family. - Added TrunkGroup Address Family.
- Added Carrier Address Family. - Added Carrier Address Family.
- Added some more references. - Added some more references.
11. Changes since -02 12. Changes since -02
- Removed the requirements section. - Removed the requirements section.
- Discussed the motivation for introducing Carrier information into - Discussed the motivation for introducing Carrier information into
TRIP. TRIP.
- Defined a new attribute for the E.164 address family. - Defined a new attribute for the E.164 address family.
- Defined a new address family for CarrierCode-TrunkGroup - Defined a new address family for CarrierCode-TrunkGroup
combination . combination .
- Defined new attributes to advertise dynamic gateway - Defined new attributes to advertise dynamic gateway
characteristics like resource availability, and call success characteristics like resource availability, and call success
rate. rate.
- Added as section to validate the TGREP solution against the - Added as section to validate the TGREP solution against the
requirements in [7]. requirements in [7].
12. Changes since -01 13. Changes since -01
- Added requirements. - Added requirements.
- Added more formal analysis of REGISTER and added analysis of SLP. - Added more formal analysis of REGISTER and added analysis of SLP.
- Removed circuit capacity attribute. - Removed circuit capacity attribute.
13. Changes since -00 14. Changes since -00
- Added text to stress the value of this proposal for managing a - Added text to stress the value of this proposal for managing a
gateway cluster. gateway cluster.
- Added attributes for circuit capacity and DSP capacity. - Added attributes for circuit capacity and DSP capacity.
- Added section on LS operation, discussing aggregation issue. - Added section on LS operation, discussing aggregation issue.
Authors' Addresses Authors' Addresses
Manjunath Bangalore Manjunath Bangalore
Cisco Systems Cisco Systems
Mail Stop SJC-21/2/2 Mail Stop SJC-21/2/2
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
email: manjax@cisco.com email: manjax@cisco.com
Rajneesh Kumar Rajneesh Kumar
Cisco Systems Cisco Systems
Mail Stop SJC-21/2/2 Mail Stop SJC-14/4/2
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
email: rajneesh@cisco.com email: rajneesh@cisco.com
Jonathan Rosenberg Jonathan Rosenberg
dynamicsoft dynamicsoft
72 Eagle Rock Avenue 72 Eagle Rock Avenue
First Floor First Floor
East Hanover, NJ 07936 East Hanover, NJ 07936
email: jdrosen@dynamicsoft.com email: jdrosen@dynamicsoft.com
Hussein F. Salama Hussein F. Salama
Cisco Systems Cisco Systems
Mail Stop CAI1 Mail Stop CAI1
skipping to change at page 27, line 21 skipping to change at page 27, line 42
[6] J. Rosenberg, "Requirements for Gateway Registration," Internet [6] J. Rosenberg, "Requirements for Gateway Registration," Internet
Draft, Internet Engineering Task Force, Nov. 2001. Work in progress. Draft, Internet Engineering Task Force, Nov. 2001. Work in progress.
[7] ITU-T List of ITU Carrier Codes (published periodically in the [7] ITU-T List of ITU Carrier Codes (published periodically in the
ITU-T Operational Bulletin). ITU-T Operational Bulletin).
[8] J. Peterson, "An Architecture for Gateway Registration Based on [8] J. Peterson, "An Architecture for Gateway Registration Based on
Trunk Groups," Internet Draft, Internet Engineering Task Force, Feb. Trunk Groups," Internet Draft, Internet Engineering Task Force, Feb.
2002. Work in progress. 2002. Work in progress.
Full Copyright Statement Intellectual Property Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
This document and translations of it may be copied and furnished to Copies of IPR disclosures made to the IETF Secretariat and any
others, and derivative works that comment on or otherwise explain it assurances of licenses to be made available, or the result of an
or assist in its implementation may be prepared, copied, published attempt made to obtain a general license or permission for the use of
and distributed, in whole or in part, without restriction of any such proprietary rights by implementers or users of this
kind, provided that the above copyright notice and this paragraph are specification can be obtained from the IETF on-line IPR repository at
included on all such copies and derivative works. However, this http://www.ietf.org/ipr.
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 The IETF invites any interested party to bring to its attention any
revoked by the Internet Society or its successors or assigns. copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
This document and the information contained herein is provided on an Disclaimer of Validity
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING This document and the information contained herein are provided on an
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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 (2004). 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
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/