Hi Paul,
Thank you for the careful review and good suggestions. Went with almost all of
them.
Please see inline for more context.
Cheers,
Med
De : ipv6 De la part de Aitken, Paul
Envoyé : lundi 22 janvier 2024 22:50
À : Joe Clarke (jclarke) ; opsawg@ietf.org
Cc : t...@ietf.org; ts...@ietf.org
Hi Thomas,
Thank you much for preparing the writeup.
I'm not sure I received the comments mentioned in point 14 of the writeup,
though. I suspect this is because of the issues I'm having with the IETF
aliases. Please forward me offline these comments. Thanks and apologies for the
inconvenie
Med,
The following drawing indicates
the position of each bit in the encoding of the Information
Element.
No, not any more - so this should be removed.
[Med] It is useful as it indicates the bit position that is then referred to in
the new IANA registry. Updated the figure to
Hi Paul,
Thank you very much for the detailed review.
There are some points that are common to the udp spec. Will discuss those in
separate threads.
Please see inline.
Cheers,
Med
De : tsvwg De la part de Aitken, Paul
Envoyé : vendredi 19 janvier 2024 10:52
À : Joe Clarke (jclarke) ; opsawg@
Re-,
Please see inline.
Cheers,
Med
De : Aitken, Paul
Envoyé : mardi 23 janvier 2024 11:26
À : BOUCADAIR Mohamed INNOV/NET ; Joe Clarke
(jclarke) ; opsawg@ietf.org
Cc : t...@ietf.org; ts...@ietf.org; 6...@ietf.org; ip...@ietf.org
Objet : Re: [**EXTERNAL**] RE: [IPFIX] WG LC: IPFIX documents
M
Hi Paul,
> It is consistent but wrong, as the numeric value of these fields is
> meaningless. Bitfields with flags semantics don't have a meaningful
> "unsigned" value.
You raised this comment for both TCP/UDP specs.
As I mentioned in the previous message, all existing IEs of type flags are
u
Hi Paul,
(restricted the distribution lists to OPSAWG and IPFIX)
The octetArray type is especially confusing as these are really hextetArrays.
[Med] Not sure we need a new data type here as octeArray is defined as follows:
The octetArray data type has no encoding rules; it represents a raw
Re-,
Paul suggested to tag these two IEs as deprecated in favor of the new full IEs.
I do personally think this is OK (especially given what Andrew reported at:
https://mailarchive.ietf.org/arch/msg/opsawg/QNm9p8V2vKuhUX5rxBCqcxD-WAY/), but
would like to hear if there objections to proceed with
Internet-Draft draft-ietf-opsawg-tacacs-tls13-05.txt is now available. It is a
work item of the Operations and Management Area Working Group (OPSAWG) WG of
the IETF.
Title: TACACS+ TLS 1.3
Authors: Thorsten Dahm
Douglas Gash
Andrej Ota
John Heasley
Na
Internet-Draft draft-ietf-opsawg-ipfix-fixes-05.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 Cla
Internet-Draft draft-ietf-opsawg-tsvwg-udp-ipfix-07.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
Ti
Internet-Draft draft-ietf-opsawg-ipfix-tcpo-v6eh-09.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
Med,
Why does the document identify issues without proposing solutions to them all?
How and when will those other issues be fixed?
[Med] The new IEs in this I-D fix all the issues.
Then please don't write "some of".
MSB LSB
0
On Tue, Jan 23, 2024 at 1:20 AM tirumal reddy wrote:
> Hi Paul,
>
> Thanks for the review. Please see inline
>
> On Sat, 20 Jan 2024 at 03:55, Paul Wouters wrote:
>
>> Hi,
>>
>> I am assisting Rob Wilton with some documents, as so I am the (temporary)
>> responsible AD for draft-ietf-opsawg-mud-
Dear Med,
That was a mistake by me. The idnits showed nothing. All clear. Will update the
shepherd review in the next iteration.
Bets wishes
Thomas
-Original Message-
From: mohamed.boucad...@orange.com
Sent: Tuesday, January 23, 2024 11:02 AM
To: Graf Thomas, INI-NET-VNC-HCS ;
draft-
Internet-Draft draft-ietf-opsawg-mud-tls-13.txt is now available. It is a work
item of the Operations and Management Area Working Group (OPSAWG) WG of the
IETF.
Title: Manufacturer Usage Description (MUD) (D)TLS Profiles for IoT Devices
Authors: Tirumaleswar Reddy
Dan Wing
This revision
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-tls-13 addresses
comments from Paul Wouters (AD).
-Tiru
On Wed, 24 Jan 2024 at 11:05, wrote:
> Internet-Draft draft-ietf-opsawg-mud-tls-13.txt is now available. It is a
> work
> item of the Operations and Management Area
17 matches
Mail list logo
