Re: [radext] radius-fragmentation: New flag T field for the Long Extended Type

Thank you!
I have seen that it was the case in the header of the draft.

Updates: RFC6929 (if approved)  

Cheers,

Lionel

-----Message d'origine-----
De : Jim Schaad [mailto:ietf@augustcellars.com] 
Envoyé : mardi 4 mars 2014 18:35
À : MORAND Lionel IMT/OLN; 'Alan DeKok'; 'Alejandro Perez Mendez'
Cc : 'Sam Hartman'; 'Stefan Winter'; radext@ietf.org
Objet : RE: [radext] radius-fragmentation: New flag T field for the Long Extended Type

This is the reason why the fragmentation draft will have an update
relationship on RFC 6929.   This sys that anybody looking at 6929 needs to
look at this draft to see what was updated.

> -----Original Message-----
> From: radext [mailto:radext-bounces@ietf.org] On Behalf Of
> lionel.morand@orange.com
> Sent: Tuesday, March 04, 2014 7:23 AM
> To: Alan DeKok; Alejandro Perez Mendez
> Cc: Sam Hartman; Stefan Winter; radext@ietf.org
> Subject: [radext] radius-fragmentation: New flag T field for the Long
> Extended Type
> 
> I repeat my comment raised during the meeting.
> 
> RFC6929 (Std) allocates the first bit after the Extended-Type field to the
> (M)ore and the rest (7-bit) is put as reserved.
> But there is nothing about how to allocate the remaining reserved bits.
> 
> This draft allocates the second bit to (T)runcation.
> 
> The question is simple: how do we ensure that another draft will not
allocate
> the same 2nd bit to another feature? It would mean that the same Long-
> extended-type attribute would have two possible interpretations/process...
> 
> Are we only relying on living memories? :) Maybe we don't care because it
is
> an experimental document... or maybe this doc will update the RFC6929 to
> indicate that the 2nd bit is used for "T".
> 
> It is not an issue with the current draft. Just an administrative issue.
> 
> Regards,
> 
> Lionel
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
exploites
> ou copies sans autorisation. Si vous avez recu ce message par erreur,
veuillez
> le signaler a l'expediteur et le detruire ainsi que les pieces jointes.
Les
> messages electroniques etant susceptibles d'alteration, Orange decline
toute
> responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and
delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.