> for example, RFC2461 7.2.4 1st paragraph does not really fit nicely
> with L2 without linklayer address.
And it doesn't match the statements in section 4.3 and 4.4 which say when
the link-layer address options must and should be included.
Those statements have the global exceptions for link-layers that don't
have link-layer addresses.
However, when editing the document the text got too unreadable if those
exceptions where included everywhere where they apply.
> the rule for attaching
> target link-layer address option does not talk about cases on L2
> without link-layer address.
> the text is very cryptic for non-english speaker like me, i really need
> a machine-readable rulesets :-)
It's machine readable - my computer can parse the ascii charcters and
display them on the screen just fine.
Perhaps you mean machine executable? :-)
Erik
> > in order for the solicitation to have been received. If the
> > solicitation's IP Destination Address is a multicast address, the
> > Target Link-Layer option MUST be included in the advertisement.
>
> now, we MUST attach a target link-layer address option in this case,
> but how? there will be a lot more examples like this.
>
> itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
