Re: Comments on LMP draft version 04

[Kireeti Kompella <kireeti@juniper.net>]

Hi Michiel,

(speaking as an interested spectator of the CCAMP WG)

On Mon, 5 Aug 2002, Michiel van Everdingen wrote:

> It seems we have had a terminology problem on the term "link".
> According to ITU-G.852.2, a link is a set of linkConnections (=dataLinks).

I'm not sure what 'link' you are referring to here.  If you are
referring to the control channel (from the context), the control
channel is *not* a link -- per email from Yakov:

> > Note that "mutually reachable" doesn't imply that these two
> > interfaces are (directly) connected by an IP link;

> Each of these dataLinks has a termination point on both sides
> of the dataLink. These termination points can either be a 'CTP' or
> a 'TTP'.

If the issue (as you say) is terminology, it would be more helpful
to stick with IETF terminology, at least until things get sorted out.

> What is in-band ?
> The dataLinks have an in-band access point identifier. DCC connections
> are to be considered out-of-band.

Again, terminology.  To get to your real point:

> > Section 14.8: In case the test message is transmitted over the DCC
> > "with bit-oriented HDLC framing format", is this by-passing the
> > DCN ? Please spend more words on how to prevent conflicts (e.g.
> > using a proprietary PPP protocol id to prevent the test message
> > to be handled by the normal routing mechanisms of DCN ?)

I assume you mean that both the DCN and Test Messages use the same
channel/link/interface/... (e.g. DCC).

Test Messages are IP messages addressed to the node at the other
end of the TE link.  So, it should be just fine if the Test Message
gets handled by "normal routing".  As for how conflicts are resolved,
LMP messages are identified as such, and Test Messages have their own
types within LMP.  What kind of conflict do you see occurring?

Hope that helps,
Kireeti.