Re: [Idr] [BULK] Bug in draft-ietf-idr-rfc5575bis, worth fixing?

[Susan Hares <[e-mail]>]

Chrisoph and John: 

 

I’m fine with the word change as well.   I thought it was clear – but anything that helps make this very clear is fine with me. 

 

Sue 

 

From: Christoph Loibl [mailto:[e-mail]] 
Sent: Saturday, September 26, 2020 4:49 AM
To: John Scudder
Cc: idr@ietf. org; [e-mail]; Hares Susan
Subject: Re: [BULK] [Idr] Bug in draft-ietf-idr-rfc5575bis, worth fixing?

 

Hi John,

 

I agree that changing the name would do no harm.

 

Cheers

 

Christoph 

 

-- 
Christoph Loibl
[e-mail] | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at

 

 





On 25.09.2020, at 21:14, John Scudder <[e-mail]> wrote:

 

Hi All, 

 

Jie brought up another point in a unicast email. He points out that 

 

The description about component type 12 (Fragment) has been updated, the meaning of the Bitmask values is added. For Bit-6 (IsF), the new description is:

 

   IsF -  Is a fragment - match if [RFC0791] IP Header Fragment Offset is not 0.

 

This description is IMO a little bit confusing, as it simply says “is a fragment”, but the matching rule does not include the case of the first fragment (MF=1, offset=0),. Perhaps it could either update the matching rules to also include the first fragment case, or it may update the description as “fragmented and not the first segment”.

 

Let’s also discuss this before we take the document off of hold and continue its processing. Speaking for myself, I don’t find the quoted text confusing since the rule specifically says “fragment offset is not 0”, but on the other hand it would do no harm to change the description to the even-more-correct “Is a fragment other than the first” (I didn’t use “segment” as Jie does, since that’s potentially a new source of confusion; “segment” is a TCP term, not an IPv4 term, and it’s a *different* IPv6 term). 

 

Thanks,

 

—John