draft-ietf-iptel-tgrep-05.txt   draft-ietf-iptel-tgrep-06.txt 
IPTEL Working Group Manjunath Bangalore, Cisco Systems Inc. IPTEL Working Group Manjunath Bangalore, Cisco Systems Inc.
Internet Draft Rajneesh Kumar, Cisco Systems Inc. Internet Draft Rajneesh Kumar, Cisco Systems Inc.
draft-ietf-iptel-tgrep-05.txt Jonathan Rosenberg, Cisco Systems Inc. draft-ietf-iptel-tgrep-06.txt Hussein Salama, MenaNet Communications S.A.E.
February 2005 Hussein Salama, Cisco Systems Inc. July 2005 Jonathan Rosenberg, Cisco Systems Inc.
Expiration Date: August 2005 Dhaval Shah, Cisco Systems Inc. Expiration Date: January 2006 Dhaval N. Shah, Cisco Systems Inc.
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 subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any 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 is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she becomes aware will be disclosed, in accordance with
RFC 3668. 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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 August 21, 2005. This Internet-Draft will expire on January 16, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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
skipping to change at page 3, line 18 skipping to change at page 3, line 18
2 Introduction ............................................. 4 2 Introduction ............................................. 4
3 TGREP: Overview of operation ............................. 6 3 TGREP: Overview of operation ............................. 6
4 TGREP Attributes ......................................... 7 4 TGREP Attributes ......................................... 7
4.1 TotalCircuitCapacity Attribute ........................... 7 4.1 TotalCircuitCapacity Attribute ........................... 7
4.2 AvailableCircuits Attribute .............................. 9 4.2 AvailableCircuits Attribute .............................. 9
4.3 CallSuccess Attribute .................................... 10 4.3 CallSuccess Attribute .................................... 10
4.4 Prefix Attributes ........................................ 12 4.4 Prefix Attributes ........................................ 12
4.5 TrunkGroup Attribute ..................................... 13 4.5 TrunkGroup Attribute ..................................... 13
4.6 Carrier Attribute ........................................ 15 4.6 Carrier Attribute ........................................ 15
4.7 TrunkGroup and Carrier Address Families .................. 16 4.7 TrunkGroup and Carrier Address Families .................. 16
4.8 Gateway Operation ........................................ 19 4.8 Gateway Operation ........................................ 18
4.9 LS/Proxy Behavior ........................................ 21 4.9 LS/Proxy Behavior ........................................ 21
5 Security Considerations .................................. 26 5 Security Considerations .................................. 25
6 IANA Considerations ...................................... 27 6 IANA Considerations ...................................... 26
6.1 Attribute Codes .......................................... 27 6.1 Attribute Codes .......................................... 26
6.2 Address Family Codes ..................................... 27 6.2 Address Family Codes ..................................... 26
7 Change history ........................................... 28 7 Change history ........................................... 27
7.1 Changes since draft-ietf-iptel-tgrep-03.txt .............. 28 7.1 Changes since draft-ietf-iptel-tgrep-03.txt .............. 27
7.2 Changes since draft-ietf-iptel-tgrep-02.txt .............. 28 7.2 Changes since draft-ietf-iptel-tgrep-02.txt .............. 27
7.3 Changes since draft-ietf-iptel-tgrep-01.txt .............. 28 7.3 Changes since draft-ietf-iptel-tgrep-01.txt .............. 27
7.4 Changes since draft-ietf-iptel-tgrep-00.txt .............. 28 7.4 Changes since draft-ietf-iptel-tgrep-00.txt .............. 27
7.5 Changes since draft-ietf-iptel-trip-gw-00.txt ............ 29 7.5 Changes since draft-ietf-iptel-trip-gw-00.txt ............ 28
7.6 Changes since -03 ........................................ 29 7.6 Changes since -03 ........................................ 28
7.7 Changes since -02 ........................................ 29 7.7 Changes since -02 ........................................ 28
7.8 Changes since -01 ........................................ 30 7.8 Changes since -01 ........................................ 29
7.9 Changes since -00 ........................................ 30 7.9 Changes since -00 ........................................ 29
8 Acknowledgments .......................................... 30 8 Acknowledgments .......................................... 29
9 References ............................................... 30 9 References ............................................... 29
9.1 Normative References ..................................... 30 9.1 Normative References ..................................... 29
9.2 Informative References ................................... 31 9.2 Informative References ................................... 30
Authors' Addresses ....................................... 31 Authors' Addresses ....................................... 30
Intellectual Property Statement .......................... 32 Intellectual Property Statement .......................... 31
Disclaimer of Validity ................................... 33 Disclaimer of Validity ................................... 32
Copyright Statement ...................................... 33 Copyright Statement ...................................... 32
Acknowledgment ........................................... 33 Acknowledgment ........................................... 32
1. Terminology and Definitions 1. Terminology and Definitions
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 RFC 2119 [1]. document are to be interpreted as described in RFC 2119 [1].
Some other useful definitions are: Some other useful definitions are:
Circuit: A circuit is a discrete (specific) path between two or more Circuit: A circuit is a discrete (specific) path between two or more
skipping to change at page 5, line 16 skipping to change at page 5, line 16
| | | |
| GW | | GW |
> +---------+ > +---------+
// //
// //
// +---------+ // +---------+
// | | // | |
+-------------------------+ // | GW | +-------------------------+ // | GW |
| | // +---------+ | | // +---------+
| +-------------+ |/ | +-------------+ |/
| | | | TO PSTN | | | |
| | Routing | | +---------+ | | Routing | | +---------+ TO PSTN
| | Proxy | | -------> | | -----> | | Proxy | | | |
---> | | |---- | GW | ---> | | |-----------> | GW | ----->
|+---+-----+ +-----+----+ | +---------+ |+---+-----+ +-----+----+ | +---------+
|| | | | | || | | | |
|| <+-+ | |-- || <+-+ | |--
||Egress LS| |Ingress LS| | --- +---------+ ||Egress LS| |Ingress LS| | --- +---------+
|| | | | | -- | | || | | | | -- | |
|+---------+ +----------+ | -- | GW | |+---------+ +----------+ | -- | GW |
| | -- +---------+ | | -- +---------+
| | --> | | -->
+-------------------------+ +-------------------------+
+---------+ +---------+
skipping to change at page 13, line 39 skipping to change at page 13, line 39
TRIP Type Code: 20. TRIP Type Code: 20.
The TrunkGroup attribute is used to represent the list of trunkgroups The TrunkGroup attribute is used to represent the list of trunkgroups
on the gateway used to complete calls. It enables providers to route on the gateway used to complete calls. It enables providers to route
calls to destinations through preferred trunks. This attribute is calls to destinations through preferred trunks. This attribute is
relatively static. relatively static.
4.5.1. TrunkGroup Syntax 4.5.1. TrunkGroup Syntax
The TrunkGroup attribute is a variable length attribute that is The TrunkGroup attribute is a variable length attribute that is
composed of a sequence of trunkgroup length-value fields. It composed of a sequence of trunkgroup identifiers. It indicates that
indicates that the gateway can complete the call through any the gateway can complete the call through any trunkgroup identifier
trunkgroup (represented by the trunkgroup label) in the sequence. indicated in the sequence.
Each trunkgroup is a length-value field (shown in Figure 3 below). Each trunkgroup identifier is encoded as a length-value field (shown
The length field is a 1-octet unsigned numeric value. The value field in Figure 3 below). The length field is a 1-octet unsigned numeric
is a variable length alphanumeric field and is also called the value. The value field is a variable length field consisting of two
trunkgroup label field. The length field represents the size of the sub-fields, a trunk group label followed by a trunk context, the two
trunkgroup label in number of octets. The maximum length is 128 sub-fields separated by the delimiter ";" (semicolon). Both the trunk
octets. group label and the trunk context sub-fields are of variable length.
The length field represents the total size of the value field
including the delimiter.
The permissible character set for the trunk group label and the trunk
group context sub-fields and the associated ABNF [10] is per rules
outlined in [13].
The presence of TrunkGroup attribute with the length field of the The presence of TrunkGroup attribute with the length field of the
attribute as 0 signifies that the TGREP GW can terminate ALL attribute as 0 signifies that the TGREP GW can terminate ALL
trunkgroup for the given Reachable route(s). trunkgroup for the given Reachable route(s).
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 ... 7 8 9 0 1 2 3 4 5 ... 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 ... 7 8 9 0 1 2 3 4 5 ...
+---------------+--------------------+---------------+--------------------- +---------------+--------------------+---------------+---------------------
| Length | TrunkGroup Label1..| Length | TrunkGroup Label2.. | Length | TrunkGroup 1... | Length | TrunkGroup 2...
+---------------+--------------------+---------------+--------------------- +---------------+--------------------+---------------+---------------------
Figure 3: TrunkGroup Syntax Figure 3: TrunkGroup Syntax
4.5.2. Route Origination and TrunkGroup 4.5.2. Route Origination and TrunkGroup
Routes MAY be originated containing the TrunkGroupattribute. Routes MAY be originated containing the TrunkGroupattribute.
4.5.3. Route Selection and TrunkGroup 4.5.3. Route Selection and TrunkGroup
The TrunkGroup attribute MAY be used for route selection. Certain The TrunkGroup attribute MAY be used for route selection. Certain
skipping to change at page 15, line 20 skipping to change at page 15, line 20
TRIP Type Code: 19. TRIP Type Code: 19.
The Carrier attribute is used to represent the list of carriers that The Carrier attribute is used to represent the list of carriers that
the gateway uses to complete calls. It enables providers to route the gateway uses to complete calls. It enables providers to route
calls to destinations through preferred carriers. This attribute is calls to destinations through preferred carriers. This attribute is
relatively static. relatively static.
4.6.1. Carrier Syntax 4.6.1. Carrier Syntax
The Carrier attribute is a variable length attribute that is composed The Carrier attribute is a variable length attribute that is composed
of a sequence of carrier values. It indicates that the route can of a sequence of carrier identifiers. It indicates that the route
complete the call to any of the carriers represented in the sequence can complete the call to any of the carriers represented in the
of carrier values. sequence of carrier identifiers.
A Carrier value is an 8-octet ASCII-encoded string obtained by
concatenation of a CarrierIdCode and a RegionCode ( defined below ).
When the length of the Carrier value is less than 8 octets, it is
padded with NULL bytes.
The CarrierIdCode is the code assigned to a carrier by a regulatory
body operating in that region. The RegionCode represents the region
where the CarrierIdCode is assigned. The RegionCode is a qualifier
that makes the Carrier value globally unique. Regions are currently
defined to map to countries. The RegionCode should use E.164 country
code used in dialing international telephony destinations. However,
regions can evolve in the future to encompass a larger area, beyond a
country. For example, if a regulatory body in the European Union that
assigns CarrierIds to carriers in the whole of Europe, a
corresponding RegionCode would be used.
The textual concatenation of CarrierId and RegionCode forms a Each carrier identifier is encoded as a length-value field (shown in
Carrier. This Carrier is then used as an attribute of the associated Figure 4 below). The length field is a 1-octet unsigned numeric
destination. value. The value field is a variable length field.
When the scope of a CarrierIdCode is known to be unique a priori, the The permissible character set for the value field and the associated
RegionCode is superfluous and MAY be excluded from the Carrier value ABNF [10] is per rules outlined in [15]. Specifically, it carries
when advertising in a TGREP UPDATE message. This is possible when the "global-cic" or "local-cic"[15]. In case of "local-cic", the
carrier is operating within the same region where the CarrierIdCode "phonedigit-hex" part and the "cic-context" part would be separated
was assigned or if the carrier is operating in a controlled by the delimiter ";". Hence absence or presence of the delimiter can
environment of networks where CarrierId is privately defined to be be used to determine if the value is a "global-cic" or a "local-cic".
unique. The length field represents the total size of the value field
including the delimiter.
The presence of Carrier Attribute with the length field of the The presence of Carrier Attribute with the length field of the
attribute as 0 signifies that the TGREP GW can terminate ALL Carriers attribute as 0 signifies that the TGREP GW can terminate ALL Carriers
for the given Reachable route(s). for the given Reachable route(s).
0 1 2 7 0 0 1
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 .....0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 .. 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 ... 7 8 9 0 1 2 3 4 5 ...
+-------------------------------------------------------------+--------------- +---------------+--------------------+---------------+---------------------
| Carrier1 | Carrier2 .. | Length | Carrier 1... | Length | Carrier 2...
+-------------------------------------------------------------+--------------- +---------------+--------------------+---------------+---------------------
Figure 4: Carrier Syntax Figure 4: Carrier Syntax
4.6.2. Route Origination and Carrier 4.6.2. Route Origination and Carrier
Routes MAY be originated containing the Carrier attribute. Routes MAY be originated containing the Carrier attribute.
4.6.3. Route Selection and Carrier 4.6.3. Route Selection and Carrier
The Carrier attribute MAY be used for route selection. Certain The Carrier attribute MAY be used for route selection. Certain
carriers MAY be preferred over others based on provider policy. carriers MAY be preferred over others based on provider policy.
skipping to change at page 18, line 17 skipping to change at page 17, line 51
[[NOTE TO RFC-ED: Please replace XX with the IANA assigned value for [[NOTE TO RFC-ED: Please replace XX with the IANA assigned value for
the carrier address family]]. the carrier address family]].
The Application Protocol field is same as the one for the Decimal, The Application Protocol field is same as the one for the Decimal,
PentaDecimal and E.164 address families defined in TRIP[4]. The PentaDecimal and E.164 address families defined in TRIP[4]. The
Length field represents the total size of the Address field in bytes. Length field represents the total size of the Address field in bytes.
The value in the Address field represents either the TrunkGroup or The value in the Address field represents either the TrunkGroup or
the Carrier address families and the syntax is as follows: the Carrier address families and the syntax is as follows:
For the TrunkGroup Address Family, the Address field is a variable For the TrunkGroup Address Family, the Address field represents a
length alphanumeric field (trunkgroup label), where length is Trunkgroup value that is defined as specified in an
determined by the length field of the route. The maximum value of the earlier Section 4.5.1 about the TrunkGroup Attribute.
length field for this Address Family is 128 bytes.
For the Carrier Address Family, the length field represents the
length of the Address field in bytes. The Address field is a fixed
length field representing Carrier value. The format of the Carrier
value is as specified in the earlier section on "Carrier attribute"
The CarrierIdCode is the code assigned to a carrier by a regulatory
body operating in that region. The RegionCode represents the region
where the CarrierIdCode is assigned. The RegionCode is a qualifier
that makes the Carrier value globally unique. Regions are currently
defined to map to countries. The RegionCode should use E.164 country
code used in dialing international telephony destinations. However,
regions can evolve in the future to encompass a larger area, beyond a
country. For example, if a regulatory body in the European Union that
assigns CarrierIds to carriers in the whole of Europe, a
corresponding RegionCode would be used.
The textual concatenation of CarrierId and RegionCode forms a
Carrier. This is then used as a destination for routing purposes.
When the scope of a CarrierIdCode is known to be unique a priori, the For the Carrier Address Family, the Address field represents a
RegionCode is superfluous and MAY be excluded from the Carrier value Carrier value that is defined as specified in an
when advertising in a TGREP UPDATE message. This is possible when the earlier Section 4.6.1 about the Carrier Attribute.
carrier is operating within the same region where the CarrierIdCode
was assigned or if the carrier is operating in a controlled
environment of networks where CarrierId is privately defined to be
unique.
If a gateway supports any of these address families, it should If a gateway supports any of these address families, it should
include that address family as one of the Route types supported in include that address family as one of the Route types supported in
the OPEN message capability negotiation phase. the OPEN message capability negotiation phase.
The following attributes are currently defined to be used with all The following attributes are currently defined to be used with all
the address families including the TrunkGroup and Carrier address the address families including the TrunkGroup and Carrier address
families. families.
- AvailableCircuits Attribute - AvailableCircuits Attribute
skipping to change at page 23, line 43 skipping to change at page 22, line 43
+/----------------+ +/----------------+
| | | |
| | | |
| | | |
| LS | | LS |
| | | |
| | | |
| | | |
| | | |
| | | |
+----------------+ +\---------------+
\
+------------------------------------------------------+ \
| +-------------------------------+ | \
| | +-+ +-+ | | \
| | |A| |C| | | +-----+ \
| | |g| |o| | | TGREP | | \
| +-------------+ | |g| |n| +-------------+ | | -- | GW | \
+--------\---------------------------------------------+
| \ +-------------------------------+ |
| \ | +-+ +-+ | |
| \ | |A| |C| | | +-----+
| \ | |g| |o| | | TGREP | |
| +---------\---+ | |g| |n| +-------------+ | | -- | GW |
| | | | |r| |s| | | | | -- +-----+ | | | | |r| |s| | | | | -- +-----+
| | TRIP | | |e| |o| | | | +-- | | TRIP | | |e| |o| | | | +--
| | LS <----------|g<--|l<--- TGREP |-++-| +-----+ | | LS <----------|g<--|l<--- TGREP |-++-| +-----+
| | | | |a| |i| | Session | | | | | | | | | |a| |i| | Session | | | | |
| | (I-TRIP/ | | |t| |d| | Management |-++-+-------| GW | | | (I-TRIP/ | | |t| |d| | Management |-++-+-------| GW |
| | E-TRIP) | | |i| |a| | | | | +-----+ | | E-TRIP) | | |i| |a| | | | | +-----+
| | (LS-Egress) | | |o| |t| | |-+ -+- | | (LS-Egress) | | |o| |t| | |-+ -+-
| +-------------+ | |n| |i| +-------------+ | | --- +-----+ | +-------------+ | |n| |i| +-------------+ | | --- +-----+
| | | | |o| | | -- | | | | | | |o| | | -- | |
| | | | |n| | | | GW | | | | | |n| | | | GW |
skipping to change at page 28, line 29 skipping to change at page 27, line 29
7.3. Changes since draft-ietf-iptel-tgrep-01.txt 7.3. 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 Pz - 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.
7.4. Changes since draft-ietf-iptel-tgrep-00.txt 7.4. Changes since draft-ietf-iptel-tgrep-00.txt
skipping to change at page 30, line 20 skipping to change at page 29, line 20
7.9. Changes since -00 7.9. 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.
8. Acknowledgments 8. Acknowledgments
We wish to thank David Oran, Anirudh Sahoo, Kevin McDermott, Jon We wish to thank Vijay Gurbani, Li Li, Kevin McDermott, David Oran,
Peterson, Li Li and Bob Penfield for their insightful comments and Bob Penfield, Jon Peterson, Anirudh Sahoo and James Yu for their
suggestions. insightful comments and suggestions.
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Bradner, S., "Keywords for use in RFCs to Indicate Requirement [1] Bradner, S., "Keywords for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP: [2] M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP:
session initiation protocol," Request for Comments 3261, Internet session initiation protocol," Request for Comments 3261, Internet
skipping to change at page 31, line 14 skipping to change at page 30, line 14
[7] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, [7] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402,
November 1998. November 1998.
[8] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload [8] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload
(ESP)", RFC 2406, November 1998. (ESP)", RFC 2406, November 1998.
[9] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)", [9] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)",
RFC 2409, November 1998. RFC 2409, November 1998.
9.2. Informative References [10] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[10] J. Rosenberg, "Requirements for Gateway Registration," Internet 9.2. Informative References
Draft, Internet Engineering Task Force, Nov. 2001. Work in progress.
[11] ITU-T List of ITU Carrier Codes (published periodically in the [11] ITU-T List of ITU Carrier Codes (published periodically in the
ITU-T Operational Bulletin). ITU-T Operational Bulletin).
[12] J. Peterson, "An Architecture for Gateway Registration Based on [12] 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.
[13] V. Gurbani and C. Jennings, "Representing trunk groups in
tel/sip Uniform Resource Identifiers (URIs)," Internet Draft,
Internet Engineering Task Force, May 2005.
[14] J. Rosenberg, "Requirements for Gateway Registration," Internet
Draft, Internet Engineering Task Force, Nov. 2001. Work in progress.
[15] J. Yu, "New Parameters for the "tel" URI to Support Number
Portability," Internet Draft, Internet Engineering Task Force, July
2005.
Authors' Addresses Authors' Addresses
Manjunath Bangalore Manjunath Bangalore
Cisco Systems Inc. Cisco Systems Inc.
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
Phone: +1-408-853-3239
email: manjax@cisco.com email: manjax@cisco.com
Rajneesh Kumar Rajneesh Kumar
Cisco Systems Inc. Cisco Systems Inc.
Mail Stop SJC-14/4/2 Mail Stop SJC-14/4/2
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Phone: +1-408-527-6148
email: rajneesh@cisco.com email: rajneesh@cisco.com
Jonathan Rosenberg Jonathan Rosenberg
Cisco Systems Inc. Cisco Systems Inc.
Mail Stop PPY02/2 Mail Stop PPY02/2
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany Parsippany
NJ 07054 NJ 07054
Phone: +1-973-952-5060
email: jdrosen@cisco.com email: jdrosen@cisco.com
Hussein F. Salama Hussein F. Salama
Cisco Systems Inc. Cisco Systems Inc.
Mail Stop CAI1 Mail Stop CAI1
135 Abdel Aziz Fahmy Street 135 Abdel Aziz Fahmy Street
2nd Floor Apartment #3, Heliopolis 2nd Floor Apartment #3, Heliopolis
Cairo, Egypt Cairo, Egypt
email: hsalama@cisco.com Phone: +202-4166200
email: hsalama@sysdsoft.com
Dhaval N. Shah Dhaval N. Shah
Cisco Systems Inc. Cisco Systems Inc.
Mail Stop SJC-06/4/3 Mail Stop SJC-20/3/3
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Phone: +1-408-527-0436
email: dhaval@cisco.com email: dhaval@cisco.com
Intellectual Property Statement Intellectual Property Statement
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
 End of changes. 

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