Re-,
> Is it possible to use unsigned256, say that topmost bits must be
> zero, and reduced size encoding MAY be used?
That was exactly what I initially proposed, but you seemed to question the RSE
applicability
(https://mailarchive.ietf.org/arch/msg/opsawg/VfPqkyXB07fe9VEneTXZ_2Z0-BY/)
Hi Paul,
What prevails in that text is the wording in the guidance.
Made the changes to avoid confusion:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ipfix-tcpo-v6eh-15
Thanks.
Cheers,
Med
De : Aitken, Paul
Envoyé : mercredi 22 mai 2024 22:25
À : BOUCADAIR Mohamed INNOV/NET ;
Internet-Draft draft-ietf-opsawg-ipfix-tcpo-v6eh-15.txt is now available. It
is a work item of the Operations and Management Area Working Group (OPSAWG) WG
of the IETF.
Title: Extended TCP Options and IPv6 Extension Headers IPFIX Information
Elements
Authors: Mohamed Boucadair
FYI.
Please work with ITU liaison, Scott Mansfield, if the WG thinks a response
needs to be sent.
> Begin forwarded message:
>
> From: Liaison Statement Management Tool
> Subject: New Liaison Statement, "LS on the new work item ITU-T Q.MUD_IoT
> “Framework for testing and monitoring IoT
Med,
I'm not happy with the unsigned192 type. It's uncommon, specific to the
udpSafeOptions IE, and unlikely to be used again for anything else.
Is it possible to use unsigned256, say that topmost bits must be zero,
and reduced size encoding MAY be used?
Thanks,
P.
On 22/05/24 20:11, David
Med,
3.3. ipv6ExtensionHeadersFull Information Element
The value of ipv6ExtensionHeadersFull IE is encoded in fewer
octets per the guidelines in Section 6.2 of [RFC7011].
If the value "is" encoded in fewer octets, then the defined size is simply too
large. For clarity I'd say
Hi Paul,
Following up on this document as well.
Thank you for performing the reviews.
Best regards,
David Dong
IANA Services Sr. Specialist
On Tue May 14 12:48:27 2024, mohamed.boucad...@orange.com wrote:
> Hi Paul,
>
> The new version with all received reviews and comments is available
>
Hi Paul,
Following up on this document as well.
Thank you for performing the reviews.
Best regards,
David Dong
IANA Services Sr. Specialist
On Tue May 14 05:21:33 2024, mohamed.boucad...@orange.com wrote:
> Hi Paul,
>
> Thanks for double checking.
>
> I don’t think there is a conflict
Internet-Draft draft-ietf-opsawg-tacacs-tls13-10.txt is now available. It is a
work item of the Operations and Management Area Working Group (OPSAWG) WG of
the IETF.
Title: Terminal Access Controller Access-Control System Plus (TACACS+)
over TLS 1.3
Authors: Thorsten Dahm
Thanks Med, that looks great.
David, I approve the -10.
P.
On 22/05/24 07:42, mohamed.boucad...@orange.com wrote:
Hi Paul,
-10 fixes all these, including the ToC level.
Thank you.
Cheers,
Med
*De :* Aitken, Paul
*Envoyé :* mardi 21 mai 2024 22:58
*À :* BOUCADAIR Mohamed INNOV/NET ;
Hi Jouni,
Good catch. This is now fixed in -11.
Thank you for the review.
Cheers,
Med
> -Message d'origine-
> De : Jouni Korhonen via Datatracker
> Envoyé : mercredi 22 mai 2024 05:57
> À : ops-...@ietf.org
> Cc : draft-ietf-opsawg-tsvwg-udp-ipfix@ietf.org; last-
>
Internet-Draft draft-ietf-opsawg-tsvwg-udp-ipfix-11.txt is now available. It
is a work item of the Operations and Management Area Working Group (OPSAWG) WG
of the IETF.
Title: Export of UDP Options Information in IP Flow Information Export
(IPFIX)
Authors: Mohamed Boucadair
Hi Paul,
-10 fixes all these, including the ToC level.
Thank you.
Cheers,
Med
De : Aitken, Paul
Envoyé : mardi 21 mai 2024 22:58
À : BOUCADAIR Mohamed INNOV/NET ;
drafts-expert-review-comm...@iana.org
Cc : ie-doct...@ietf.org; opsawg
Objet : Re: [Ie-doctors] [IANA #1363822] Expert review
Internet-Draft draft-ietf-opsawg-ipfix-fixes-10.txt is now available. It is a
work item of the Operations and Management Area Working Group (OPSAWG) WG of
the IETF.
Title: Simple Fixes to the IP Flow Information Export (IPFIX) IANA Registry
Authors: Mohamed Boucadair
Benoit
14 matches
Mail list logo
