Re: lmp linkcorrelation error code

["Adrian Farrel" <adrian@olddog.co.uk>]

Fab,

Someone else with an implementation may care to comment (since our aim is
interoperable implementations).

Adrian


> But which one 0x01 or 0x02? Both (seems a bit contradictory)?
>
> Section 12.6.3 list the error case but I don't see which one corresponds
to
> a "wrong interface mapping".
> TE Link object and datalink object are negotiable object and interface
Ids
> are inside those objects.
> But I don't think we can considere interface (or TE link) Id as
negotiable?
>
> What do you think?
>
> Thanks
> Fab
>
>
>
> The TE
> > Fab,
> >
> > See section 13.15.
> >
> >        0x01 =Unacceptable non-negotiable LINK_SUMMARY parameters. 0x02
> >        =Renegotiate LINK_SUMMARY parameters.
> >
> > Cheers,
> > Adrian
> > ----- Original Message -----
> > From: <fab12@freesurf.fr>
> > To: <ccamp@ops.ietf.org>
> > Sent: Tuesday, February 22, 2005 7:25 AM
> > Subject: lmp linkcorrelation error code
> >
> >
> >> Hi,
> >>
> >> In draft-ietf-ccamp-lmp-10 section 4 about link corelation states
that
> >> a "LinkSummaryNack message MUST be transmitted, indicating which
> > interface
> >> mapping and/or which properties are not accepted"
> >>
> >> In case of wrong interface mapping which error code should be encoded
> >> in the linkSummaryNack?
> >>
> >> Thanks
> >> Fab
>
>
>
>
>