Specifies the physical facility ID interconnecting the two service providers in an EVC meet point configuration.
NOTE 1: MEF 26.1 defines the basic architecture of Metro Ethernet Services that cross more than one service provider domain. However, it assumes that the EVC customer interacts with only one provider who in turn places “access” orders (ENNI for the physical interconnect and OVCs for the virtual service instance) to all other providers in the path. The EVC customer receives a single circuit ID. Also in the MEF 26.1 model, this “EVC Meet Point” would actually be an ENNI and the EVC customer would have no visibility to it. The EVC Meet Point ID field supports an alternative, pre-MEF 26.1 model whereby the EVC customer places the EVC order simultaneously to both service providers in the end to end path and refers to the physical interconnection point between the two providers.
NOTE 2: Established during pre-order negotiations outside of the ASR process.
NOTE 3: The interconnecting facility requires that an Ethernet port be dedicated to it in order to carry Ethernet service, when the EVC involves the territories of more than one provider.
NOTE 4: The format and structure of this field is defined in the ANSI approved standard, ATIS-0300097, Structure for the Identification of Telecommunications Connections for the North American Telecommunications System or by COMMON LANGUAGE in BR-795-450-100. A brief summary of the format can be found in ATIS-0404000 Section 2.14.5.
VALID ENTRIES:
CLFI Code
NOTE 1: The facility type code and CLLI codes used in the location elements of the CLFI code are maintained by Telcordia Technologies.
USAGE: This field is conditional.
NOTE 1: Optional when the ASC-EC field on the ASR form is populated, otherwise prohibited.
DATA CHARACTERISTICS: 42 alpha/numeric characters
EXAMPLE: 1 0 1 / G E I N / C I T Y S T 2 5 1 1 W
/ C I T Y S T X A 1 3 W