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

RE: LMP Procedure in UNI 1.0 - Doubts



Ramesh:

At least the 1st question of your message belongs to the OIF
lists and not to the IETF lists. If you want to follow up,
please post to oif-signal@oiforum.com <mailto:oif-signal@oiforum.com>  or
send private mail.
 
In any case, let me just briefly answer the questions:
 
(1) Neighbor discovery runs only between network elements
and not proxies. If there is a proxy, information must be configured.
 
(2) Node ID refers to the single unique Id of the node (an IP address)
     Interface ID is an ID for a data link interface. E.g., could be a
locally
     unique index. 
     CCID is an ID for the control channel. One CC could be used to
     control interactions over multiple link interfaces. In the in-fiber
case,
     a one-to-one association between CC and data link is assumed, hence
    the relation CCID = interface ID.
 
regards,
 
Bala

-----Original Message-----
From: S Ramesh [mailto:rashanmu@npd.hcltech.com]
Sent: Sunday, October 14, 2001 3:40 PM
To: CCAMP; GMPLS
Cc: mpls@UU.NET
Subject: LMP Procedure in UNI 1.0 - Doubts


Hi,
 
I have some doubts in UNI 1.0 Whitepaper published by OIF.
 
1. IN section 8.2 it is given the UNI neighbour discovery  mechanism is
based on the LMP protocol mechanism. It is defined some three identifiers
for LMP procedures NodeID,CCID, INterfaceID. For in-fiber case the CCID MUST
be equal to the Interface ID. if this is the case then under direct service
invocation model which supports In-fiber method, there exists a proxy UNI-N
on the TNE side. So here the CCID cannot be the the same as the interface id
because interface id is the port address for data transfer and the CCID is
the IP control channel which can be a seperate point to point link between
the UNI-C and the proxy UNI-N. Then how comes the criteria
 
CCID == Interface ID ( MUST in in-fiber case) can be satisfied.
 
2. Also there is some confusion exists regarding the three IDs as i
mentioned above. When Config messages are sent under IP encapsulation they
use the destination address as the Node ID of the destination. So what is
the interface ID. Can anybody kindly explain these three IDs with a specific
scenario.
 
Thanks,
Ramesh