Hi Pascal,
This is a very good addition. It is needed for devices that have very limited
resources. Battery devices in the utility industry sleep for periods of time
and are not conducive to the discovery methods that require broadcast.
I do have few comments:
- In the introduction
Ok everyone, please excuse the fumbling of the new guy. My previous comments
were actually for this draft, not the one I indicated earlier. Please disregard
my last email.
Repeated, now for the correct draft:
Hi Pascal,
This is a very good addition. It is needed for devices that have very limi
: Falendysz, Gene
Cc: 6lo@ietf.org
Subject: Re: New Version Notification for
draft-thubert-6lo-multicast-registration-00.txt
Hello Gene
Many thanks for your review and comments!
And welcome to the list : )
Please see below
> Le 4 oct. 2021 à 19:28, Falendysz, Gene a écrit :
>
> Ok
Pascal,
Thanks for addressing my earlier comments. Below is one for the latest draft.
In section 8 the following sentence seems to be improperly formed. " When
encapsulating an packet with an IPv4 multicast
Destination Address, it MUST use form a multicast address and use the
appropriate
All,
I support draft-thubert-6lo-multicast-registration-02 adoption. It is a
needed addition for sleepy end devices in 6lo networks.
Gene Falendysz
864-723-1395
-Original Message-
From: 6lo <6lo-boun...@ietf.org> On Behalf Of Carles Gomez Montenegro
Sent: Monday, October 18, 2021 10:2
Hi Pascal,
The draft does not currently address the "All Nodes Addresses" discussed in
RFC 4291. Because there is a requirement that a node accept the link local
scope All Nodes address, this should not require the 6LN to register to have
this address forwarded. The 6LR should forward these im
All,
This draft covers a very real need in the support of battery operated devices
in a Wi-SUN FAN network. The draft, as presented, meets our need. Anything that
can be done to expedite its approval would be appreciated.
Best regards,
Gene Falendysz
864-723-1395
-Original Message-
Hi Pascal,
In section 7.3 is this statement:
"That asynchronous NA(ARO) SHOULD be sent to the all-nodes link scope multicast
address (FF02::1) and Target MUST be set to the link local address that was
exposed previously by this node to accept registrations, and the TID MUST be
set to 0."
Why t
request, incrementing with each power
cycle.
Best regards,
Gene Falendysz
Office:(864)718-6676 / Mobile: (864)723-1395
-Original Message-
From: Pascal Thubert (pthubert)
Sent: Friday, November 18, 2022 6:09 AM
To: Falendysz, Gene ; 6lo@ietf.org
Subject: [EXTERNAL] RE: [6lo] WG Last Call on
That sounds like it will work. Thanks for addressing our use case.
Gene Falendysz
Office:(864)718-6676 / Mobile: (864)723-1395
-Original Message-
From: Pascal Thubert (pthubert)
Sent: Friday, November 18, 2022 9:46 AM
To: Falendysz, Gene ; Pascal Thubert (pthubert)
; 6lo@ietf.org
Hi Pascal,
I think this will work.
Gene Falendysz
Office:(864)718-6676 / Mobile: (864)723-1395
-Original Message-
From: Pascal Thubert (pthubert)
Sent: Tuesday, November 22, 2022 3:49 AM
To: Falendysz, Gene ; 6lo@ietf.org
Subject: RE: [6lo] WG Last Call on draft-ietf-6lo-multicast
Looks good.
Gene Falendysz
Office:(864)718-6676 / Mobile: (864)723-1395
-Original Message-
From: Pascal Thubert (pthubert)
Sent: Tuesday, November 22, 2022 10:57 AM
To: Falendysz, Gene ; fa...@wi-sun.org; 6lo@ietf.org
Subject: RE: [6lo] WG Last Call on draft-ietf-6lo-multicast
I too support adoption. I also concur with Pascal's statements of need.
Gene Falendysz
(Office) 864-718-6676 (cell) 864-723-1395
From: 6lo <6lo-boun...@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: Thursday, July 13, 2023 7:35 AM
To: 6lo@ietf.org; carles.go...@upc.edu
Subject: [EXTERNAL]
13 matches
Mail list logo