Re: [tcpm] SYN/ACK Payloads, draft 01

Hi Lars,
Of course, I know that but thanks for clarifying :)
We used a value just for experimentation purposes only.
What Adam was saying is that TCP option kind values 254 and 255 were
reserved to specify a length indicator, that's what I understood. But I
think he meant 253 and 254. Anyway, these kind values seem to not be
reserved for a specific purposed... instead, they are reserved for
experimentation purposes. Also, just to clarify this. :)
Regards,
Sergio

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com] 
Sent: terça-feira, 12 de Agosto de 2008 15:48
To: ext Sergio Freire
Cc: 'Adam Langley'; andre.zuquete@ua.pt; tcpm@ietf.org
Subject: Re: [tcpm] SYN/ACK Payloads, draft 01

On 2008-8-12, at 16:44, ext Sergio Freire wrote:
> Sergio: Well I don't think that is exactly correct. Looking
athttp://www.iana.org/assignments/tcp-parameters/ 
>  and RFC3692 and RFC4727, we can see that the reserved kind values  
> are 253 and 254. These two are used for testing purposes as RFC3692  
> (I think for general testing purposes, not for a specific purpose).  
> So, a new option would have to be assigned to specify a way of  
> extending the available space for TCP options. In a first phase I  
> guess 253 or 254 could be used for that since they are "generic", if  
> what I've said earlier is correct.

If you look at the URL you posted, you'll see this bit: "Registration  
Procedures: IESG Approval or Standards Action"

That means that you MUST obtain a number through one of these two  
procedures (see RFC5226). You MUST NOT simply grab an unassigned one.

Adam is correct that for limited experimentation, you should use 253  
or 254, as per RFC4727. To go beyond that, you MUST register an option  
number, either via IESG Approval or a Standards Action.

Lars

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm