draft-ietf-ccamp-transport-lmp-01.txt   draft-ietf-ccamp-transport-lmp-02.txt 
Network Working Group Don Fedyk (Nortel Networks) Network Working Group Don Fedyk (Nortel Networks)
Internet Draft Osama Aboul-Magd (Nortel Networks) Internet Draft Osama Aboul-Magd (Nortel Networks)
Category: Informational Deborah Brungard (AT&T) Category: Informational Deborah Brungard (AT&T)
Expires August 2005 Jonathan Lang (Sonos, Inc.) Expires October 2005 Jonathan Lang (Sonos, Inc.)
Dimitri Papadimitriou (Alcatel) Dimitri Papadimitriou (Alcatel)
February 2005 May 2005
A Transport Network View of the Link Management Protocol A Transport Network View of the Link Management Protocol
<draft-ietf-ccamp-transport-lmp-01.txt> <draft-ietf-ccamp-transport-lmp-02.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 RFC 3668. 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
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 Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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."
skipping to change at line 60 skipping to change at line 61
1. ASON Terminology and Abbreviations related to Discovery.........2 1. ASON Terminology and Abbreviations related to Discovery.........2
1.1 Terminology....................................................2 1.1 Terminology....................................................2
1.2 Abbreviations.................................................3 1.2 Abbreviations.................................................3
2. Introduction....................................................3 2. Introduction....................................................3
3. Transport Network Architecture..................................4 3. Transport Network Architecture..................................4
3.1 G.8080 Discovery Framework.....................................6 3.1 G.8080 Discovery Framework.....................................6
4. Discovery Technologies..........................................8 4. Discovery Technologies..........................................8
4.1 Generalized automatic discovery techniques G.7714..............8 4.1 Generalized automatic discovery techniques G.7714..............8
4.2 LMP and G.8080 Terminology Mapping.............................9 4.2 LMP and G.8080 Terminology Mapping.............................9
4.2.1 TE Link Definition and Scope................................11 4.2.1 TE Link Definition and Scope................................10
4.3 LMP and G.8080 Discovery Relationship.........................12 4.3 LMP and G.8080 Discovery Relationship.........................12
4.4 Comparing LMP and G.8080......................................13 4.4 Comparing LMP and G.8080......................................13
5. Security Considerations........................................13 5. Security Considerations........................................13
6. IANA Considerations............................................14 6. IANA Considerations............................................14
7. Intellectual Property Considerations...........................14 7. Intellectual Property Considerations...........................14
8. References.....................................................15 8. References.....................................................15
8.1 Normative References..........................................15 8.1 Normative References..........................................15
8.2 Informational References......................................15 8.2 Informational References......................................15
9. Acknowledgements...............................................16 9. Acknowledgements...............................................16
10. Author's Addresses............................................16 10. Author's Addresses............................................16
skipping to change at line 82 skipping to change at line 83
12. Full Copyright Statement......................................17 12. Full Copyright Statement......................................17
1. ASON Terminology and Abbreviations related to Discovery 1. ASON Terminology and Abbreviations related to Discovery
1.1 Terminology 1.1 Terminology
The reader is assumed to be familiar with the terminology in [LMP] The reader is assumed to be familiar with the terminology in [LMP]
and [LMP-TEST]. The following ITU-T terminology/abbreviations are and [LMP-TEST]. The following ITU-T terminology/abbreviations are
used in this document: used in this document:
Access Group (AG): A group of co-located "trail termination"
functions that are connected to the same "subnetwork" or "link".
Access Point (AP): A "reference point" that consists of the pair of
co-located "unidirectional access" points, and therefore represents
the binding between the trail termination and adaptation functions.
Connection Point (CP): A "reference point" that consists of a pair Connection Point (CP): A "reference point" that consists of a pair
of co-located "unidirectional connection points" and therefore of co-located "unidirectional connection points" and therefore
represents the binding of two paired bidirectional "connections". represents the binding of two paired bidirectional "connections".
Connection Termination Point (CTP): A Connection Termination Point Connection Termination Point (CTP): A Connection Termination Point
(CTP) represents the state of a CP [M.3100]. (CTP) represents the state of a CP [M.3100].
Characteristic Information: Signal with a specific format, which is Characteristic Information: Signal with a specific format, which is
transferred on "network connections". The specific formats will be transferred on "network connections". The specific formats will be
defined in the technology specific Recommendations. For trails the defined in the technology specific Recommendations. For trails the
Characteristic Information is the payload plus the overhead. The Characteristic Information is the payload plus the overhead. The
information transferred is characteristic of the layer network. information transferred is characteristic of the layer network.
D. Fedyk, Editor Informational 2
Link: a subset of ports at the edge of a subnetwork or access group Link: a subset of ports at the edge of a subnetwork or access group
which are associated with a corresponding subset of ports at the which are associated with a corresponding subset of ports at the
edge of another subnetwork or access group. edge of another subnetwork or access group.
Link Connection (LC): a transport entity that transfers information Link Connection (LC): a transport entity that transfers information
between ports across a link. between ports across a link.
D. Fedyk, Editor Informational 2
Network Connection (NC): A concatenation of link and subnetwork Network Connection (NC): A concatenation of link and subnetwork
connections. connections.
Subnetwork: a set of ports which are available for the purpose of Subnetwork: a set of ports which are available for the purpose of
routing 'characteristic information'. routing 'characteristic information'.
Subnetwork Connection (SNC): a flexible connection that is setup and Subnetwork Connection (SNC): a flexible connection that is setup and
released using management or control plane procedures. released using management or control plane procedures.
Subnetwork Point (SNP): SNP is an abstraction that represents an Subnetwork Point (SNP): SNP is an abstraction that represents an
actual or potential underlying connection point (CP) or termination actual or potential underlying connection point (CP) or termination
connection point (TCP) for the purpose of control plane connection point (TCP) for the purpose of control plane
representation. representation.
Subnetwork Point Pool (SNPP): A set of SNP that are grouped together Subnetwork Point Pool (SNPP): A set of SNP that are grouped together
for the purpose of routing for the purpose of routing.
Termination Connection Point (TCP): A reference point that Termination Connection Point (TCP): A reference point that
represents the output of a Trail Termination source function or the represents the output of a Trail Termination source function or the
input to a Trail Termination sink function. A network connection input to a Trail Termination sink function. A network connection
represents a transport entity between TCPs. represents a transport entity between TCPs.
.
Trail Termination source/sink function: A "transport processing Trail Termination source/sink function: A "transport processing
function" which accepts the characteristic information of the layer function" which accepts the characteristic information of the layer
network at its input, removes the information related to "trail" network at its input, removes the information related to "trail"
monitoring and presents the remaining information at its output. monitoring and presents the remaining information at its output.
Unidirectional Connection: A "transport entity" which transfers Unidirectional Connection: A "transport entity" which transfers
information transparently from input to output. information transparently from input to output.
Unidirectional Connection Point: A "reference point" that represents Unidirectional Connection Point: A "reference point" that represents
the binding of the output of a "unidirectional connection" to the the binding of the output of a "unidirectional connection" to the
input of another "unidirectional connection". input of another "unidirectional connection".
skipping to change at line 154 skipping to change at line 148
LMP: Link Management Protocol LMP: Link Management Protocol
OTN: Optical transport network OTN: Optical transport network
PDH: Plesiosynchronous digital hierarchy PDH: Plesiosynchronous digital hierarchy
SDH: Synchronous digital hierarchy. SDH: Synchronous digital hierarchy.
2. Introduction 2. Introduction
D. Fedyk, Editor Informational 3
The GMPLS control plane consists of several building blocks as The GMPLS control plane consists of several building blocks as
described in [GMPLS-ARCH]. The building blocks include signaling, described in [RFC3945]. The building blocks include signaling,
routing, and link management for establishing LSPs. For scalability routing, and link management for establishing LSPs. For scalability
purposes, multiple physical resources can be combined to form a purposes, multiple physical resources can be combined to form a
single traffic engineering (TE) link for the purposes of path single traffic engineering (TE) link for the purposes of path
computation and GMPLS control plane signaling. computation and GMPLS control plane signaling.
D. Fedyk, Editor Informational 3
As manual provisioning and management of these links is impractical As manual provisioning and management of these links is impractical
in large networks, LMP was specified to manage TE links. Two in large networks, LMP was specified to manage TE links. Two
mandatory management capabilities of LMP are control channel mandatory management capabilities of LMP are control channel
management and TE link property correlation. Additional optional management and TE link property correlation. Additional optional
capabilities include verifying physical connectivity and fault capabilities include verifying physical connectivity and fault
management. [LMP] defines the messages and procedures for GMPLS TE management. [LMP] defines the messages and procedures for GMPLS TE
link management. [LMP-TEST] defines SONET/SDH specific messages and link management. [LMP-TEST] defines SONET/SDH specific messages and
procedures for link verification. procedures for link verification.
ITU-T Recommendation G.8080 Amendment 1 [G.8080] defines control ITU-T Recommendation G.8080 Amendment 1 [G.8080] defines control
skipping to change at line 206 skipping to change at line 200
architecture forms the basis for a set of technology specific architecture forms the basis for a set of technology specific
architectural recommendations for transport networks (e.g., SDH, architectural recommendations for transport networks (e.g., SDH,
PDH, OTN, etc.) PDH, OTN, etc.)
The architecture defined in G.805 is designed using a layered model The architecture defined in G.805 is designed using a layered model
with a client-server relationship between layers. The architecture with a client-server relationship between layers. The architecture
is recursive in nature; a network layer is both a server to the is recursive in nature; a network layer is both a server to the
client layer above it and a client to the server layer below it. client layer above it and a client to the server layer below it.
There are two basic building blocks defined in G.805: "subnetworks" There are two basic building blocks defined in G.805: "subnetworks"
and "links". A subnetwork is defined as a set of ports which are and "links". A subnetwork is defined as a set of ports which are
D. Fedyk, Editor Informational 4
available for the purpose of routing "characteristic information". A available for the purpose of routing "characteristic information". A
link consists of a subset of ports at the edge of one subnetwork (or link consists of a subset of ports at the edge of one subnetwork (or
"access group") and is associated with a corresponding subset of "access group") and is associated with a corresponding subset of
ports at the edge of another subnetwork or access group. ports at the edge of another subnetwork or access group.
Two types of connections are defined in G.805: "link connection" Two types of connections are defined in G.805: "link connection"
(LC) and "subnetwork connection" (SNC). A link connection is a fixed (LC) and "subnetwork connection" (SNC). A link connection is a fixed
D. Fedyk, Editor Informational 4
and inflexible connection, while a subnetwork connection is flexible and inflexible connection, while a subnetwork connection is flexible
and is setup and released using management or control plane and is setup and released using management or control plane
procedures. A network connection is defined as a concatenation of procedures. A network connection is defined as a concatenation of
subnetwork and link connections. Figure 1 illustrates link and subnetwork and link connections. Figure 1 illustrates link and
subnetwork connections. subnetwork connections.
(++++++++) (++++++++) (++++++++) (++++++++)
( SNC ) LC ( SNC ) ( SNC ) LC ( SNC )
(o)--------(o)----------(o)--------(o) (o)--------(o)----------(o)--------(o)
( ) CP CP ( ) ( ) CP CP ( )
skipping to change at line 447 skipping to change at line 441
Note that the table maps ASON terms to GMPLS terms that refer to Note that the table maps ASON terms to GMPLS terms that refer to
equivalent objects, but in many cases there is not a one to one equivalent objects, but in many cases there is not a one to one
mapping. Additional information beyond Discovery terminology can be mapping. Additional information beyond Discovery terminology can be
found in [LEXICO]. found in [LEXICO].
D. Fedyk, Editor Informational 9 D. Fedyk, Editor Informational 9
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| ASON Terms | GMPLS/LMP Terms | GMPLS/LMP Terms | | ASON Terms | GMPLS/LMP Terms | GMPLS/LMP Terms |
| | Port | Component Link | | | Port | Component Link |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| AP | Unidirectional | Unidirectional |
| | Data Port | Data Port |
+----------------+--------------------+-------------------+
| CP | TE Resource; | TE Resource; | | CP | TE Resource; | TE Resource; |
| | Interface (Port) | Interface. | | | Interface (Port) | Interface. |
| | |(Comp. link) | | | |(Comp. link) |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| CP Name | Interface ID | Interface ID(s) | | CP Name | Interface ID | Interface ID(s) |
| | no further sub- | resources (such as| | | no further sub- | resources (such as|
| | division for(label)| timeslots, etc.) | | | division for(label)| timeslots, etc.) |
| | resource allocation| on this interface | | | resource allocation| on this interface |
| | | are identified by | | | | are identified by |
| | | set of labels | | | | set of labels |
skipping to change at line 474 skipping to change at line 465
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNP | TE Resource | TE Resource | | SNP | TE Resource | TE Resource |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNP Name | Link ID | Link ID | | SNP Name | Link ID | Link ID |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNP LC | TE Link | TE Link | | SNP LC | TE Link | TE Link |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNP LC Name | TE Link ID | TE Link ID | | SNP LC Name | TE Link ID | TE Link ID |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNPP | TE Link End | TE Link End | | SNPP | TE Link End | TE Link End |
| | (Port) | Comp. Link) | | | (Port) | (Comp. Link) |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNPP Name | Link ID | Link ID | | SNPP Name | Link ID | Link ID |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNPP Link | TE Link | TE Link | | SNPP Link | TE Link | TE Link |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
| SNPP Link Name | TE Link ID | TE Link ID | | SNPP Link Name | TE Link ID | TE Link ID |
+----------------+--------------------+-------------------+ +----------------+--------------------+-------------------+
where composite identifiers are: where composite identifiers are:
- Data Link ID: <Local Interface ID; Remote Interface ID> - Data Link ID: <Local Interface ID; Remote Interface ID>
- TE Link ID: <Local Link ID; Remote Link ID> - TE Link ID: <Local Link ID; Remote Link ID>
Composite Identifiers are defined in the LMP draft [LMP]. LMP Composite Identifiers are defined in the LMP draft [LMP]. LMP
discovers Data Links and identifies them by the pair of local and discovers Data Links and identifies them by the pair of local and
remote interface Ids. TE Links are comprised of Data Links or remote interface Ids. TE Links are comprised of Data Links or
component TE links. TE links are similarly identified by pair of component TE links. TE links are similarly identified by pair of
local and remote Link ID. local and remote Link ID.
D. Fedyk, Editor Informational 10
4.2.1 TE Link Definition and Scope 4.2.1 TE Link Definition and Scope
D. Fedyk, Editor Informational 10
In the table, TE link/resource is equated with the concept of SNP, In the table, TE link/resource is equated with the concept of SNP,
SNP LC, SNPP and SNPP link. The definition of the TE link is broad in SNP LC, SNPP and SNPP link. The definition of the TE link is broad in
scope and it is useful to repeat it here. The original definition scope and it is useful to repeat it here. The original definition
appears in [GMPLS-RTG]: appears in [GMPLS-RTG]:
"A TE link is a logical construct that represents a way to group/map "A TE link is a logical construct that represents a way to group/map
the information about certain physical resources (and their the information about certain physical resources (and their
properties) that interconnects LSRs into the information that is properties) that interconnects LSRs into the information that is
used by Constrained SPF for GMPLS path computation, and GMPLS used by Constrained SPF for GMPLS path computation, and GMPLS
signaling." signaling."
skipping to change at line 532 skipping to change at line 522
Since TE links may represent large numbers of parallel resources Since TE links may represent large numbers of parallel resources
they can be bundled for efficient summarization of resource they can be bundled for efficient summarization of resource
capacity. Typically bundling represents a logical TE link resource capacity. Typically bundling represents a logical TE link resource
at a particular Interface Switching Capability. Once TE link at a particular Interface Switching Capability. Once TE link
resources are allocated the actual capacity may be represented as resources are allocated the actual capacity may be represented as
LSP hierarchical (tunneled) TE link capability in another logical TE LSP hierarchical (tunneled) TE link capability in another logical TE
link [HIER]. link [HIER].
TE links also incorporate the notion of a Forwarding Adjacency (FA) TE links also incorporate the notion of a Forwarding Adjacency (FA)
and Interface Switching Capability [GMPLS-ARCH]. The FA allows and Interface Switching Capability [RFC3945]. The FA allows
transport resources to be represented as TE-links. The Interface transport resources to be represented as TE-links. The Interface
Switching Capability specifies the type of transport capability such Switching Capability specifies the type of transport capability such
as Packet Switch Capable(PSC), Layer-2 Switch Capable (L2SC), as Packet Switch Capable(PSC), Layer-2 Switch Capable (L2SC),
Time-Division Multiplex (TDM), Lambda Switch Capable (LSC) and Time-Division Multiplex (TDM), Lambda Switch Capable (LSC) and
Fiber-Switch Capable (FSC). Fiber-Switch Capable (FSC).
A TE link between GMPLS controlled optical nodes may consist of a A TE link between GMPLS controlled optical nodes may consist of a
bundled (TE link) which itself consists of a mix of point-to-point bundled (TE link) which itself consists of a mix of point-to-point
component links [BUNDLE]. A TE link is identified by the tuple: component links [BUNDLE]. A TE link is identified by the tuple:
(Bundled link Identifier(32 bit number), Component link (link Identifier (32 bit number), Component link Identifier (32 bit
Identifier(32 bit number) and generalized label(media specific)). number) and generalized label (media specific)).
D. Fedyk, Editor Informational 11 D. Fedyk, Editor Informational 11
4.3 LMP and G.8080 Discovery Relationship 4.3 LMP and G.8080 Discovery Relationship
LMP currently consists of four primary procedures, of which, the LMP currently consists of four primary procedures, of which, the
first two are mandatory and the last two are optional: first two are mandatory and the last two are optional:
1. Control channel management 1. Control channel management
2. Link property correlation 2. Link property correlation
skipping to change at line 692 skipping to change at line 682
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 ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
D. Fedyk, Editor Informational 14 D. Fedyk, Editor Informational 14
8. References 8. References
8.1 Normative References 8.1 Normative References
[RFC3668] S. Bradner, "Intellectual Property Rights in IETF [BCP 78] S. Bradner, "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3668, February 2004. Technology", BCP 79, RFC 3667, February 2004.
[BCP 79] S. Bradner, "IETF Rights in Contributions", BCP 79,
RFC 3668, February 2004.
8.2 Informational References 8.2 Informational References
[LMP] J.P.Lang (Editor), "Link Management Protocol," draft- [LMP] J.P.Lang (Editor), "Link Management Protocol," draft-
ietf-ccamp-lmp-10.txt, October 2003. ietf-ccamp-lmp-10.txt, October 2003.
[LMP-TEST] J.P.Lang et al., "SONET/SDH Encoding for Link [LMP-TEST] J.P.Lang et al., "SONET/SDH Encoding for Link
Management Protocol (LMP) Test messages," draft-ietf- Management Protocol (LMP) Test messages," draft-ietf-
draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt, December draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt, December
2004. 2004.
skipping to change at line 719 skipping to change at line 712
Switching (GMPLS)Signaling Functional Description," Switching (GMPLS)Signaling Functional Description,"
RFC3471, January 2003. RFC3471, January 2003.
[GMPLS-RTG] K. Kompella & Y. Rekhter (editors) "Routing Extensions [GMPLS-RTG] K. Kompella & Y. Rekhter (editors) "Routing Extensions
in Support of Generalized Multi-Protocol Label in Support of Generalized Multi-Protocol Label
Switching", draft-ietf-ccamp-gmpls-routing-09.txt, Switching", draft-ietf-ccamp-gmpls-routing-09.txt,
December 2003. December 2003.
[HIER] K. Kompella & Y. Rekhter "LSP Hierarchy with Generalized [HIER] K. Kompella & Y. Rekhter "LSP Hierarchy with Generalized
MPLS TE", draft-ietf-mpls-lsp-hierarchy-08.txt, MPLS TE", draft-ietf-mpls-lsp-hierarchy-08.txt,
September 2002 September 2002.
[BUNDLE] K. Kompella, Y. Rekhter, Lou Berger "Link Bundling in [BUNDLE] K. Kompella, Y. Rekhter, Lou Berger "Link Bundling in
MPLS Traffic Engineering", draft-ietf-mpls-bundle- MPLS Traffic Engineering", draft-ietf-mpls-bundle-
06.txt, December 2004 06.txt, December 2004.
[LEXICO] A. Farrel & I Bryskin "A Lexicography for the [LEXICO] A. Farrel & I Bryskin "A Lexicography for the
Interpretation of Generalized Multiprotocol Label Interpretation of Generalized Multiprotocol Label
Switching (GMPLS) Terminology within The Context of the Switching (GMPLS) Terminology within The Context of the
ITU-T's Automatically Switched Optical Network (ASON) ITU-T's Automatically Switched Optical Network (ASON)
Architecture", draft-bryskin-ccamp-gmpls-ason- Architecture", draft-bryskin-ccamp-gmpls-ason-
lexicography-00.txt, February 2005 lexicography-02.txt, April 2005.
"For information on the availability of ITU-T Documents, please see "For information on the availability of ITU-T Documents, please see
http://www.itu.int" http://www.itu.int"
D. Fedyk, Editor Informational 15
[G.783] ITU-T G.783 (2004), Characteristics of synchronous [G.783] ITU-T G.783 (2004), Characteristics of synchronous
digital hierarchy (SDH) equipment functional blocks. digital hierarchy (SDH) equipment functional blocks.
D. Fedyk, Editor Informational 15
[G.805] ITU-T G.805 (2000), Generic functional architecture of [G.805] ITU-T G.805 (2000), Generic functional architecture of
transport networks. transport networks.
[G.7714] ITU-T G.7714/Y.1705 (2001), Generalized automatic [G.7714] ITU-T G.7714/Y.1705 (2001), Generalized automatic
discovery techniques. discovery techniques.
[G.7714.1] ITU-T G.7714.1/Y.1705.1 (2003), Protocol for automatic [G.7714.1] ITU-T G.7714.1/Y.1705.1 (2003), Protocol for automatic
discovery in SDH and OTN networks. discovery in SDH and OTN networks.
[G.8080] ITU-T G.8080/Y.1304 (2001), Architecture for the [G.8080] ITU-T G.8080/Y.1304 (2001), Architecture for the
automatically switched optical network (ASON). automatically switched optical network (ASON).
[M.3100] ITU-T M.3100 (1995), Generic Network Information Model [M.3100] ITU-T M.3100 (1995), Generic Network Information Model.
[T.50] ITU-T T.50 (1992), International Reference Alphabet [T.50] ITU-T T.50 (1992), International Reference Alphabet.
9. Acknowledgements 9. Acknowledgements
The authors would like to thank Astrid Lozano, John Drake, Adrian The authors would like to thank Astrid Lozano, John Drake, Adrian
Farrel and Stephen Shew for their valuable comments. Farrel and Stephen Shew for their valuable comments.
The authors would like to thank ITU-T Study Group 15 Question 14 for The authors would like to thank ITU-T Study Group 15 Question 14 for
their careful review and comments. their careful review and comments.
10. Author's Addresses 10. Author's Addresses
skipping to change at line 780 skipping to change at line 773
Email: dwfedyk@nortel.com Email: dwfedyk@nortel.com
Osama Aboul-Magd Osama Aboul-Magd
Nortel Networks Nortel Networks
P.O. Box 3511, Station 'C' P.O. Box 3511, Station 'C'
Ottawa, Ontario, Canada Ottawa, Ontario, Canada
K1Y-4H7 K1Y-4H7
Phone: +1 613 763-5827 Phone: +1 613 763-5827
Email: osama@nortel.com Email: osama@nortel.com
D. Fedyk, Editor Informational 16
Deborah Brungard Deborah Brungard
AT&T AT&T
Rm. D1-3C22 Rm. D1-3C22
200 S. Laurel Ave. 200 S. Laurel Ave.
Middletown, NJ 07748, USA Middletown, NJ 07748, USA
Email: dbrungard@att.com Email: dbrungard@att.com
D. Fedyk, Editor Informational 16
Jonathan P. Lang Jonathan P. Lang
Sonos, Inc. Sonos, Inc.
506 Chapala Street 506 Chapala Street
Santa Barbara, CA 93101 Santa Barbara, CA 93101
Email : jplang@ieee.org Email : jplang@ieee.org
Dimitri Papadimitriou Dimitri Papadimitriou
Alcatel Alcatel
Francis Wellesplein, 1 Francis Wellesplein, 1
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
 End of changes. 

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