Re: [secdir] draft-ietf-tcpm-tcpsecure

["Anantha Ramaiah (ananth)" <[e-mail]>]

 

>
> 
> > secure is mostly useful only for long lived connections (like BGP), 
> > then it may not be applicable to hosts and only applicable 
> to routers. 
> > I
> 
> So what?  Implementors who don't care for this feature 
> wouldn't be bound to implement it just because this RFC says 
> it's a MUST.  Implementors who don't implement it would just 
> not be compliant with this RFC, but nothing says they have to be.

Well, we did argue this point before.

> 
> > didn't (so as many others) didn't buy this argument, but 
> since it was 
> > not going anywhere Lars stepped up with the suggestion of 
> > applicability statement to be added to this draft (I 
> haven't seen any 
> > other TCP related RFC which has an AS in it, FWIW) and the rest is 
> > history. I seriously doubt whether the chairs/Lars/WG would like to 
> > fallback to MUST/MUST/SHOULD.
> 
> I'd like to hear from them.

Sure, but if you can also suggest some text (either in the AS section or
in section 6) which can probably make the implementers more comfortable
and also can make look the compliance story healhier we can consider
adding such a text and take care of this issue. As an FYI, I want to
stress that the draft has been around for a long time before reaching
last call and I would prefer not to move backwards. That said, if the
consensus turns out to be changing the mitigation stengths as per your
suggestion, I am fine with that too!

> 
> > As far as the SYN corner case workaround we chose not to talk about 
> > the fix for the same in the draft since the corner case 
> exists in RFC 
> > 793 and nothing to do with the current SYN mitigation.
> 
> OK.  Maybe this should be stated in the I-D.

The draft already covers it in section 4.2. "This corner case is a
result of the [RFC0793] specification and is
not introduced by these new requirements."  

Do you see the need for more clarification?, if so pl feel free to send
some text.

-Anantha
> 
> Nico
> -- 
>