[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: [ANCP] Layer 2 Parameters in the Protocol document



Menachem,

 

The usage of a VPI/VCI is really dependent on the use case you are considering.

Regarding the use case access line topology it is optional because there is no strong relation to a layer 2 parameter if we report the net data rate.

 

But considering the use cases OAM (F5 LB for ADSL2/2plus) or line configuration the layer 2 parameter such as VPI/VCI or VLAN is essential. So I would recommend keeping these layer 2 parameters in the format of the “Access-Loop-Circuit-ID”.

 

Regards

 

Thomas

 


Von: Menachem.Dodge at ecitele.com [mailto:Menachem.Dodge at ecitele.com]
Gesendet: Montag, 28. August 2006 15:57
An: ancp at ietf.org; swadhwa at juniper.net; jmoisand at juniper.net; ssubramanian at juniper.net; Haag, Thomas; norbert.voigt at siemens.com
Betreff: [ANCP] Layer 2 Parameters in the Protocol document

 


Hi,

        I have a question regarding the "Access-Loop-Circuit-ID" as defined in the document "draft-wadhwa-gsmp-l2control-configuration-01.txt".

        In the case of an Ethernet based local loop the format is defined as:

        "Access-Node-Identifier eth slot/port[:vlan-id]" meaning that the vlan-id is optional.

        In the case of an ATM based local loop the format is defined as:

        "Access-Node-Identifier atm slot/port:vpi.vci"  meaning that the vpi.vci is mandatory.

        I would like this changed to "Access-Node-Identifier atm slot/port[:vpi.vci]" meaning that the vpi.vci is optional.

        This would allow for multiple vpi/vci(s) on the same port as a message could be sent  without the vpi.vci field.


===========================================================================

I have a similar question regarding the "Access-Aggregation-Circuit-ID-ASCII" as defined in the document "draft-wadhwa-gsmp-l2control-configuration-01.txt".

        In the case of an Ethernet based local loop the format is defined as:

        "Access-Node-Identifier eth slot/port[:inner-vlan-id][:outer-vlan-id]" meaning that the vlan-ids are optional.

        In the case of an ATM based local loop the format is defined as:

        "Access-Node-Identifier atm slot/port:vpi.vci"  meaning that the vpi.vci is mandatory.

        I would like this changed to "Access-Node-Identifier atm slot/port[:vpi.vci]" meaning that the vpi.vci is optional.

       
Thank you kindly.

Best Regards,
Menachem

_______________________________________________
ANCP mailing list
ANCP at ietf.org
https://www1.ietf.org/mailman/listinfo/ancp