Fernando,

On 9/27/2006 2:03 AM, Fernando Gont allegedly said the following:
> At 23:48 26/09/2006, Carlos Pignataro wrote:
> 
>>> * In several parts the draft talks about ICMP types, and includes in
>>> the same list "destination unreachable, parameter problem, etc.".
>>> However, "parameter problem" (and others) are *codes* of the same
>>> type ("destination unreachable"). This should be fixed.
>> The only instance I found is:
>>
>>       An ICMP Extension Structure MAY be appended to ICMPv4 Destination
>>       Unreachable, Time Exceeded, and Parameter Problem messages.
>>
>> Are you referring to this one?
>>
>> In any case, "Parameter problem" is ICMP Type 12 [RFC792] and a new code
>> (for this type) from [RFC1122], "Time Exceeded" is Type 11, and
>> "Destination Unreachable" is ICMP Type 3 (with >~ 13 codes).
> 
> Oops, sorry. For some reason I had in my head that time exceeded and 
> others were different codes of "destination unreachable".
> Forget this, then. :-)
> 
> 
> 
>>> * The header in Figure 1 includes a "Next-Hop MTU" field. However,
>>> this field is included only in "frag needed and DF bit set", but not
>>> for the other message codes.
>> Yes; this is introduced in rev -07, since the text after figure 1 in -06 is:
>>    The syntax and semantics of all fields are unchanged from RFC 792 and
>>    RFC 1191.  However, a length attribute is added to the second word.
>>
>> It should be fixed (as it was before, or somesuch adding that "Next-Hop
>> MTU" is only for "fragmentation needed and DF set")
> 
> Agreed.
> 
> 
>>> * Page 5, section 4:
>>> "   RFC 1191 [4] adds a "Next-Hop MTU" field to the Destination
>>>     Unreachable message."
>>>
>>> As explained in the previous bullet, RFC 1191 modifies only "frag
>>> needed and DF bit set"
>> Agreed. How about?
>>
>>    RFC 1191 [4] adds a "Next-Hop MTU" field to the Destination
>>    Unreachable message with code indicating "fragmentation needed and DF
>>    set".
> 
> Good.
> 
> P.S.: Note that RFC 1812 (?) defines a whole bunch of ICMP messages 
> (eg, "communication administratively forbidden..."). If the list in 
> draft-bonica was meant to mention all ICMP messages, it should list 
> those ones, too.

"Communication Administratively Prohibited" is code 13 for Destination
Unreachable type of 3 (like you say, from RFC1812); related codes for
the type are 9 and 10 from RFC1122.

Thanks,

--Carlos.

> 
> Kindest regards,
> 
> --
> Fernando Gont
> e-mail: [EMAIL PROTECTED] || [EMAIL PROTECTED]
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 

-- 
--Carlos Pignataro.
Escalation RTP - cisco Systems

_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area

Reply via email to