Re: [6tisch] WGLC for draft-ietf-roll-dao-projection

if you see anything wrong / inappropriate in that work. All the best to you all; Pascal > -Original Message- > From: RAW On Behalf Of Pascal Thubert (pthubert) > Sent: jeudi 5 janvier 2023 10:22 > To: r...@ietf.org > Cc: det...@ietf.org; 6tisch@ietf.org > Subject: [R

[6tisch] WGLC for draft-ietf-roll-dao-projection

Dear all As you know, in particular with the discussion on the term "Track", ROLL is reusing terminology from RAW. This is done in particular in draft-ietf-roll-dao-projection. As it goes, the draft also has a discussion on how the specification could be used for RAW in section 3.7.2.4 https

Re: [6tisch] time to close WG

Hello Michael We kept it open in case new work comes up. This might happen once RAW has progressed to the point that it requires interfaces that 6TiSCH can implement in the 802.15.4 TSCH case. Maybe we can observe RAW, wait and see ? Keep safe; Pascal > -Original Message- > From: 6tis

[6tisch] Finally !!

Dear all It is our greatest pleasure to announce that the following RFCs were just published on the IETF data tracker: RFC 9030 (was draft-ietf-6tisch-architecture) An Architecture for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4

[6tisch] Nomcom needs you

NomCom is considering nominees for AD positions, IETF Chair, IAB, LLC Board, and IETF Trust. We need more input from the community both on specific nominees and on over-arching topics regarding what the community wants from these specific groups and wants from its leadership in general. We need

[6tisch] FW: [802.15-ALL] Sad news about Dr. Robert F. Heile

Dear all, I thought you wanted to know. Bob was the chair of IEEE 802.15 for a great many years. From: pat.kin...@kinneyconsultingllc.com Sent: vendredi 25 septembre 2020 18:13 To: stds-802-w...@listserv.ieee.org Subject: [802.15-ALL] Sad news about Dr. Robert F. Heile It is with my greatest re

[6tisch] FW: New Version Notification for draft-ietf-6tisch-architecture-29.txt

/cluster_info.php?cid=C310, longing for the unaware leaves, the MSF, the CORE stateless and the enhanced beacons drafts. Keep safe! Pascal -Original Message- From: internet-dra...@ietf.org Sent: jeudi 27 août 2020 11:38 To: Pascal Thubert (pthubert) Subject: New Version Notification for

[6tisch] Fwd: Nomcom 2020-2021 Second Call For Volunteers

As Fred says... non-com is a foundation of the IETF open and diverse activities. Please volunteer if you can... Pascal Expéditeur: Fred Baker Date: 11 juin 2020 à 00:02:17 UTC+2 Destinataire: IPv6 Operations Objet: [v6ops] Fwd: Nomcom 2020-2021 Second Call For Volunteers  Folks: the nomcom c

Re: [6tisch] Benjamin Kaduk's No Objection on draft-ietf-6tisch-msf-16: (with COMMENT)

session". Though the performance of MSF is evaluated only when the "selected parent" represents the node's preferred parent, there This tells me that the handling of Benjamin’s review is not complete, so I asked Tengfei to double check. Take care; Pascal From: Te

Re: [6tisch] Benjamin Kaduk's No Objection on draft-ietf-6tisch-msf-16: (with COMMENT)

To: Benjamin Kaduk Cc: The IESG ; draft-ietf-6tisch-...@ietf.org; 6tisch <6tisch@ietf.org>; 6tisch-cha...@ietf.org; Pascal Thubert (pthubert) Subject: Re: [6tisch] Benjamin Kaduk's No Objection on draft-ietf-6tisch-msf-16: (with COMMENT) Hi Benjamin, Thanks for updating the c

Re: [6tisch] MSF traffic adaptation under stress

Hello David I’m really interested to see your results and proposal for improvements. If people are interested we could set up an hour virtual interim. We must have it 3 weeks in advance which means early June. In the meantime, yes please consider whether there are simple adjustments to the spe

Re: [6tisch] Benjamin Kaduk's Discuss on draft-ietf-6tisch-msf-12: (with DISCUSS and COMMENT)

Hello Ben ´ > Le 3 avr. 2020 à 05:37, Benjamin Kaduk a écrit : > > Hi Pascal, > >> On Thu, Apr 02, 2020 at 09:57:07AM +0000, Pascal Thubert (pthubert) wrote: >> Hello Benjamin and authors: >> >> Thomas is really the MAC expert, (virtually) collocated with

Re: [6tisch] Benjamin Kaduk's Discuss on draft-ietf-6tisch-msf-12: (with DISCUSS and COMMENT)

Hello Benjamin and authors: Thomas is really the MAC expert, (virtually) collocated with him, and more fluent in English than I'll ever be. But I'll take a chance at it. I understand that the problem you're concerned with happens when the automatic slot offset for node A ends up the same as tha

Re: [6tisch] Alissa Cooper's Discuss on draft-ietf-6tisch-enrollment-enhanced-beacon-13: (with DISCUSS and COMMENT)

gt; Cc: The IESG ; Pascal Thubert (pthubert) > ; 6tisch-cha...@ietf.org; 6tisch@ietf.org; draft-ietf- > 6tisch-enrollment-enhanced-bea...@ietf.org > Subject: Re: [6tisch] Alissa Cooper's Discuss on draft-ietf-6tisch-enrollment- > enhanced-beacon-13: (with DISCUSS and COMMENT) &g

[6tisch] Fwd: REMINDER: Early Bird Cutoff is Monday, February 3rd at 23:59

Regards, Pascal Début du message transféré : Expéditeur: "Rob Wilton (rwilton)" Date: 3 février 2020 à 17:22:03 UTC+1 Destinataire: "ietf-interest(mailer list)" Objet: FW: REMINDER: Early Bird Cutoff is Monday, February 3rd at 23:59 A reminder that the early bird cutoff for IETF 107 is a

Re: [6tisch] Secdir last call review of draft-ietf-6tisch-enrollment-enhanced-beacon-06

Hello Michael I agree with the format you selected, things are readable this way. There are 2 or 3 typos in the new text that can be fixed with the editor. Also I’m happy with the conclusions you made on the possible attacks. All the best, Pascal > Le 22 janv. 2020 à 23:21, Michael Richardson

Re: [6tisch] New Version Notification for draft-karaagac-6tisch-int-00.txt

l Message- >> >> From: 6tisch [mailto:6tisch-boun...@ietf.org] On Behalf Of Pascal Thubert >> (pthubert) >> Sent: Tuesday, January 14, 2020 10:11 PM >> To: Abdulkadir Karaağaç (UGent-imec) ; >> 6tisch@ietf.org >> Subject: Re: [6tisch] New Version Noti

Re: [6tisch] New Version Notification for draft-karaagac-6tisch-int-00.txt

Dear authors This draft strikes me as very mature for a 00, and a very useful piece of work as well. It looks like you have implemented and tried it out already, correct? A few comments and questions: * Since you are using IEs Fig 1 could represent the insertion before the IPv6 payload. * Ther

Re: [6tisch] WGLC on draft-ietf-6tisch-msf-09

My issues seem resolved Tengfei I’ll make a pass tomorrow and if / when I get all the authors to answer me on the IPR I’ll make the publication request. Regards, Pascal Le 12 déc. 2019 à 18:29, Tengfei Chang a écrit :  Hi All, As you may notice that the draft-ietf-6tisch-msf-09 is just

[6tisch] hepherd write up for draft-ietf-6tisch-msf: IPR statement

Dear all It is time to publish draft-ietf-6tisch-msf, and as part of the process I need to confirm whether there is IPR on this specification. Authors: please confirm whether any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have alr

Re: [6tisch] MSF adapts to traffic only for secured packets

uyuki Tanaka mailto:yasuyuki.tan...@inria.fr>> wrote: Thank you, all. The proposed text looks very good to me. It resolves my concerns. Best, Yatch On 12/12/2019 6:01 AM, Tengfei Chang wrote: > Cool! Thanks for the additional info! Integrated as well! > > On Thu, Dec 12, 2019 at

[6tisch] Fwd: Protocol Action: 'Constrained Join Protocol (CoJP) for 6TiSCH' to Proposed Standard (draft-ietf-6tisch-minimal-security-15.txt)

Malisa and all: great work and congrats!!! Pascal Début du message transféré : Expéditeur: The IESG Date: 11 décembre 2019 à 21:09:50 UTC+1 Destinataire: IETF-Announce Cc: The IESG , "Pascal Thubert (pthubert)" , "Pascal Thubert (pthubert)" , "6tisch-cha...@ietf.org&

Re: [6tisch] MSF Shepherd review

ting. Then replace the sentence in the draft from "preferred parent" to "selected parent". What are your comments on this, Pascal, Yatch? On Sat, Nov 30, 2019 at 12:31 AM Pascal Thubert (pthubert) mailto:pthub...@cisco.com>> wrote: Hello Yatch > Le 29 nov. 2019

Re: [6tisch] MSF adapts to traffic only for secured packets

sense, I could consider the DSCP value can be another information stored at upper layer that MSF have read access to it. Thinking in this way, it seems OK for me. Do you agree such interpreting? Tengfei On Thu, Dec 5, 2019 at 5:50 PM Pascal Thubert (pthubert) mailto:pthub...@cisco.com>>

Re: [6tisch] MSF adapts to traffic only for secured packets

Hello Tengfei Architecturally speaking, MSF right now is used to allocate cells in the L3 bundle with a parent. “ Layer-2 vs. Layer-3 bundle: Bundles are associated for either Layer-2 (switching) or Layer-3 (routing) forwarding operations. A pair of Layer-3 bundles (one for each direction) map

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-minimal-security-13: (with DISCUSS and COMMENT)

Regards, Pascal > Le 5 déc. 2019 à 04:06, Mirja Kuehlewind a écrit : > > Hi Michael, > > Sorry for my late reply (but I guess you could have just went ahead and push > a new version anyway…). Please see below. > >>> On 1. Nov 2019, at 22:15, Michael Richardson wrote: >>> >>> >>> <#sec

Re: [6tisch] MSF Shepherd review

Hello Yatch > Le 29 nov. 2019 à 22:48, Yasuyuki Tanaka a écrit : > > Thank you, Pascal for your comment. > >> On 11/29/2019 9:34 PM, Pascal Thubert (pthubert) wrote: >> RPL underneath is designed to operate with multiple parents, and for a good >> reason

Re: [6tisch] MSF Shepherd review

t; a 6P transaction with a DODAG. > > In any case, I prefer having "the preferred parent" in the text, > although "parent" sounds like a L3 term. L2 doesn't maintain > parent-child relationships. > > My two cents. > > Best, > Yatch > > >> O

Re: [6tisch] MSF Shepherd review

frame traffic load results an average 4 cells scheduled, using the value of double number of scheduled cells (which is 8) as MAX_NUM_CELLS gives a good resolution on cell usage calculation. Any recommendation on the rephrasing? Tengfei On Wed, Nov 27, 2019 at 10:07 PM Pascal Thubert (pth

Re: [6tisch] MSF Shepherd review

Any recommendation on the rephrasing? Tengfei On Wed, Nov 27, 2019 at 10:07 PM Pascal Thubert (pthubert) mailto:pthub...@cisco.com>> wrote: Hello Tengfei Please see below Le 27 nov. 2019 à 21:44, Tengfei Chang mailto:tengfei.ch...@gmail.com>> a écrit :  Thanks a lot for

Re: [6tisch] MSF Shepherd review

Hello Tengfei Please see below Le 27 nov. 2019 à 21:44, Tengfei Chang a écrit :  Thanks a lot for the reviewing, I responded inline: On Mon, Nov 25, 2019 at 6:42 PM Pascal Thubert (pthubert) mailto:pthub...@cisco.com>> wrote: Dear all Please find some comments below: Please migr

[6tisch] MSF Shepherd review

Dear all Please find some comments below: Please migrate to XML2RFC v3. This will save time in the future. However, an implementor MAY implement MSF without implementing Minimal 6TiSCH Configuration. This is not helpful without explanations. What is the tradeoff? How does the net

[6tisch] MSF review

Hello Yatch Many thanks again for agreeing to perform another review one the latest MSF.. Once this is last round is complete, the shepherd will perform the request for publication. All the best, Pascal ___ 6tisch mailing list 6tisch@ietf.org https:/

[6tisch] tentative agenda for Singapore

Dear all We published a draft agenda for Singapore at https://datatracker.ietf.org/doc/agenda-106-6tisch/ Like in Montreal Mališa Vučinić and I will be seating at the chairs positions, Thomas being remote. Please have a look and let us know if any change is needed. All the best, Pascal __

Re: [6tisch] WGLC for draft-ietf-6tisch-msf-07

Dear all The WGLC has now completed. I asked the authors to publish before cutoff based on the comments raised so we can have a status at the IETF meeting. I'll start a shepherd review based on that level. All the best Pascal From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Pas

[6tisch] Remote presentations at IETF106 - cutoff date November 16

Dear all: Please keep in mind that remote presenters need a meetecho access. So please do not forget to tell me as part of your presentation proposal that you'll be remote, and I'll make sure you're listed with meetecho. Also, cutoff date is approaching to normal rate and draft publication htt

[6tisch] 6TiSCH @ IETF 106: Call for agenda items

Dear 6TiSCHers, The agenda for IETF 106 has been published at: https://datatracker.ietf.org/meeting/106/agenda.html. Keep this link, it's always useful with a number of pointers to meeting needful things. Also consider the IETF application for your smartphone... So 6TISCH will be meeting on Fr

[6tisch] WGLC for draft-ietf-6tisch-msf-07

Dear WG : We are launching a WG last call for MSF https://tools.ietf.org/html/draft-ietf-6tisch-msf-07 . The call starts today and runs for 2 weeks, ending November 1st. This leaves a small window around the week end to publish final changes before the draft publication cutoff on November 4th.

Re: [6tisch] downstream traffic adaptation

ndredi 4 octobre 2019 07:25 To: Pascal Thubert (pthubert) Cc: 6tisch <6tisch@ietf.org> Subject: Re: [6tisch] downstream traffic adaptation Hi Pascal, Yes, it is implemented and tested, the result is shown in the (long) email "[6tisch] validating the downstream traffic adaptation in

Re: [6tisch] Roman Danyliw's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

others on what the result of the attack can be - and indicate the 350 years. Please ssee if that's enough. All the best, Pascal > -Original Message- > From: Michael Richardson > Sent: mardi 27 août 2019 19:44 > To: Tero Kivinen > Cc: Pascal Thubert (pthubert) ; R

Re: [6tisch] I-D Action: draft-ietf-6tisch-architecture-26.txt

Many thanks Michael! Regards, Pascal > Le 27 août 2019 à 19:31, Michael Richardson a écrit : > > > internet-dra...@ietf.org wrote: >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-6tisch-architecture-26 > > The updates in -26 are mostly te

Re: [6tisch] [Roll] WG adoption call for draft-richardson-6tisch-roll-enrollment-priority-02 - Extended (fwd) Ines Robles: [Roll] WG adoption call for draft-richardson-6tisch-roll-enrollment-priority-

+1 Regards, Pascal > Le 27 août 2019 à 20:09, Michael Richardson a écrit : > > > This document is part of the enhanced beacon process. > Comments appreciated to *ADOPT*. > > > ___ > 6tisch mailing list > 6tisch@ietf.org > https://www.ietf.org/mai

Re: [6tisch] Roman Danyliw's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

All the best, Pascal > -Original Message- > From: Tero Kivinen > Sent: mardi 27 août 2019 15:01 > To: Pascal Thubert (pthubert) > Cc: Roman Danyliw ; The IESG ; Benjamin > Kaduk ; shwetha.bhand...@gmail.com; 6tisch@ietf.org; > 6tisch-cha...@ietf.org; draft-

Re: [6tisch] Roman Danyliw's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

to be published soon. Please come back to us if this needs additional work : ) All the best, Pascal > -Original Message- > From: Roman Danyliw > Sent: jeudi 22 août 2019 22:57 > To: Pascal Thubert (pthubert) ; The IESG > > Cc: draft-ietf-6tisch-architect...@ietf.org;

Re: [6tisch] downstream traffic adaptation

Looks good Tengfei. Did you already implement and test? Pascal From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Tengfei Chang Sent: vendredi 23 août 2019 14:28 To: 6tisch <6tisch@ietf.org> Subject: [6tisch] downstream traffic adaptation Hi All, As discussed in IETF 105, we are going to suppo

Re: [6tisch] cell rules in MSF

Hello Tengfei The text below: whether there is any incoming frame on those cells could be understood like it is a unicast frame to this node. In fact the text should describe promiscuous listening of traffic between arbitrary nodes. I’m OK to use carrier sense since an interference is only inter

[6tisch] moving on with MSF

Dear authors At IETF 105, we mentioned that 2 issues were remaining and that we'd last call by fall. Which is soon. I'd like to restart the discussion and I'm asking you to start a thread for each of these issues so we can solve them and move forward. The ball is in you camp. Many thanks : )

[6tisch] Normative references in Archie

Dear all : Following the latest round of IESG reviews and upon a suggestion by Mirja seconded by Benjamin, we promoted a number of references to normative in https://tools.ietf.org/html/draft-ietf-6tisch-architecture-25 This means that Archie will not ship until all of these references are RFC.

Re: [6tisch] Intelligent JP / validating the MASA

s? Pascal > -Original Message- > From: Benjamin Kaduk > Sent: vendredi 23 août 2019 01:49 > To: Michael Richardson > Cc: Pascal Thubert (pthubert) ; =?utf- > 8?B?TWFsacWhYSBWdcSNaW5pxIc=?= ; Tero Kivinen > ; 6tisch@ietf.org > Subject: Re: Intelligent JP / valid

Re: [6tisch] Roman Danyliw's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

Hello Roman: I elided the pieces where we are in sync > > > ** Section 6. Per “Section 9 of [RFC8453] applies equally to > > > 6TiSCH”, this reference organizes threats and mitigations around the > > > CMI and MPI interfaces. > > > What is the analog to those in this architecture? > > > > PT>

Re: [6tisch] Roman Danyliw's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

Hello Roman: Many thanks for your review, your time is much appreciated. Please see below: > > -- > COMMENT: > -- > > ** Why are both Section 3.4 and Section

Re: [6tisch] Benjamin Kaduk's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

Hello Benjamin: Many thanks for your in depth review of the draft, this is really appreciated. Please see below: > -- > DISCUSS: > -- > > Section 4.3.4 asserts:

Re: [6tisch] Intelligent JP / validating the MASA

issue. Mališa On 20 Aug 2019, at 18:20, Pascal Thubert (pthubert) mailto:pthub...@cisco.com>> wrote: Dear all: I’m looking for a consensus on how to address the following review comment on the 6TiSCH Architecture by Benjamin: > I'd like to see some discussion somewhere that the

Re: [6tisch] rekeying the 6TiSCH network

best, Pascal > -Original Message- > From: Don Sturek > Sent: mardi 20 août 2019 22:17 > To: Michael Richardson ; Pascal Thubert (pthubert) > ; Benjamin Kaduk ; Mališa Vučinić > ; Tero Kivinen ; 6tisch@ietf.org > Subject: Re: [6tisch] rekeying the 6TiSCH network &g

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

oyé le :mercredi 21 août 2019 11:59 À : Pascal Thubert (pthubert)<mailto:pthub...@cisco.com> Cc : Suresh Krishnan<mailto:suresh.krish...@gmail.com>; Shwetha Bhandari<mailto:shwetha.bhand...@gmail.com>; 6tisch@ietf.org<mailto:6tisch@ietf.org>; 6tisch-cha...@ietf.org<mailto:6

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

rrect reflection of what those drafts specify. Please let me know if that matches the need that you identified, Pascal > -Original Message- > From: Pascal Thubert (pthubert) > Sent: mardi 20 août 2019 18:06 > To: Mirja Kuehlewind > Cc: Suresh Krishnan ; Shwetha Bhandari

Re: [6tisch] rekeying the 6TiSCH network

t, Pascal > -Original Message- > From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Michael Richardson > Sent: mardi 20 août 2019 22:03 > To: Pascal Thubert (pthubert) ; Benjamin Kaduk > ; =?iso-8859-2?Q?Mali=B9a_Vu=E8ini=E6?= > ; Tero Kivinen ; 6tisch@ietf.org > Subj

[6tisch] Intelligent JP / validating the MASA

Dear all: I'm looking for a consensus on how to address the following review comment on the 6TiSCH Architecture by Benjamin: > I'd like to see some discussion somewhere that the Join Proxy needs to take > care > to not be an open redirector by which an unauthenticated pledge can attack > ar

[6tisch] rekeying the 6TiSCH network

Dear all: I'm looking for a consensus on how to address the following review comment on the 6TiSCH Architecture by Benjamin: > It would be good to see some architectural discussion about key management > for the link-layer keys. (Given that 802.15.4 leaves key management as out of > scope,

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

T) > > See below. > > > On 8. Aug 2019, at 18:05, Pascal Thubert (pthubert) > wrote: > > > > Hello Suresh and Mirja > > > > I’m happy to get recommendations on that topic. I understand Mirja’s > recommendation on how to use normative refs; it makes sen

Re: [6tisch] Éric Vyncke's No Objection on draft-ietf-6tisch-architecture-24: (with COMMENT)

Hello Eric : ) Many thanks for your kind review. Please see below > -- > COMMENT: > -- > > Pascal, > > Thank you for the hard work put into this document. It

Re: [6tisch] starting WGLC for draft-ietf-6tisch-enrollment-enhanced-beacon-02

ch <6tisch-boun...@ietf.org> On Behalf Of Pascal Thubert (pthubert) Sent: vendredi 26 juillet 2019 19:32 To: 6tisch@ietf.org Subject: [6tisch] starting WGLC for draft-ietf-6tisch-enrollment-enhanced-beacon-02 Dear all This is officially starting a 3 weeks WGLC window for https://tools.ietf.org/h

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

ontent will be something like this, we can rephrase it later. Please let me know what you think. Thanks! Tengfei On Mon, Jul 22, 2019 at 5:35 PM Tero Kivinen mailto:kivi...@iki.fi>> wrote: Pascal Thubert (pthubert) writes: > In a 6TiSCH network, CCA is useless between synchronized

Re: [6tisch] Benjamin Kaduk's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

Great! We asked for that change at the time, and clearly it was implemented. This means that the text in the Architecture is now obsolete and I’ll remove it. Many thanks Tero. Pascal > Le 8 août 2019 à 23:58, Tero Kivinen a écrit : > > Benjamin Kaduk via Datatracker writes: >> ---

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

, Pascal Le 8 août 2019 à 16:01, Suresh Krishnan mailto:suresh.krish...@gmail.com>> a écrit : Hi Mirja, On Thu, Aug 8, 2019, 6:29 AM Mirja Kuehlewind mailto:i...@kuehlewind.net>> wrote: Hi Pascal, See below. > On 7. Aug 2019, at 20:31, Pascal Thubert (pthubert) > mailto:pthub...

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

ailed content of final version of the > referenced draft. > > As I said I’m not the person to make a final judgement call here, but your > reply below indicates to me that the concept of informative vs. normative was > not considered correctly and needs to be double-checked. > >

Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)

Hello Mirja Your time is appreciated, many thanks for considering this draft. The 6TiSCH Architecture has been a WIZp throughout the lifespan of the WG. It may be seen as its main product, most of the needed components being requested from other WGs. This may be unusual but that was the plan f

Re: [6tisch] ASN replay attack -- proposed text

All good, I expected it and wanted confirm : ) All the best, Pascal > -Original Message- > From: Mališa Vučinić > Sent: mardi 30 juillet 2019 05:24 > To: Pascal Thubert (pthubert) > Cc: Thomas Watteyne ; 6tisch <6tisch@ietf.org> > Subject: Re: ASN replay

Re: [6tisch] ASN replay attack -- proposed text

Agreed: I'm wondering about the delayed security processing. That processing may be delayed beyond the current ASN. Is the ASN of the receive time attached to the frame as a meta of sorts to enable the delayed validation? All the best, Pascal > -Original Message- > From: 6tisch <6tisc

[6tisch] draft-tiloca-6tisch-robust-scheduling

Dear Pat: This is about https://datatracker.ietf.org/doc/draft-tiloca-6tisch-robust-scheduling/ This work was presented at 6TiSCH at this and previous IETFs, and we wanted to follow up with you and the 6TiSCH IG. Basically, we recognize that the technique can be valuable to protect the TSCH med

[6tisch] starting WGLC for draft-ietf-6tisch-enrollment-enhanced-beacon-02

Dear all This is officially starting a 3 weeks WGLC window for https://tools.ietf.org/html/draft-ietf-6tisch-enrollment-enhanced-beacon-02, a longer period than usual to cover possible vacation time. Please send comments by August 16th 2019. Many thanks in advance The chairs _

[6tisch] Agenda bashing

Dear all Please note that the agenda for 6TiSCH @ IETF 105 (https://datatracker.ietf..org/doc/agenda-105-6tisch/) was amended to place Marco at the very end in order to address a WG collision. All the best Pascal ___ 6tisch mailing list 6tisch@ietf.

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

draft and make it optional. All the best, Pascal From: Tengfei Chang Sent: mercredi 17 juillet 2019 08:32 To: Pascal Thubert (pthubert) Cc: 6tisch@ietf.org Subject: Re: [6tisch] call for review: draft-ietf-6tisch-msf-04 Hi Pascal, It is good for me to confirm it is about the hidden terminal

Re: [6tisch] New datatracker feature: Allow presenters to upload slides

Dear all: On the side, please keep in mind that the chromebooks only play PDFs, and use that form to upload your slides. All the best, Pascal From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Pascal Thubert (pthubert) Sent: lundi 15 juillet 2019 07:22 To: lp-...@ietf.org; 6tisch@ie

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

ent: mercredi 17 juillet 2019 06:12 To: Pascal Thubert (pthubert) Cc: 6tisch@ietf.org Subject: Re: [6tisch] call for review: draft-ietf-6tisch-msf-04 Hi Pascal, For the synchronization, I agree. It should be listening for a certain period of time and then choose which EB to use for synchronizing. W

[6tisch] Fwd: New datatracker feature: Allow presenters to upload slides

Dear all, Please see below, you can now upload your slides directly ! Regards, Pascal Début du message transféré : Expéditeur: Robert Sparks mailto:rjspa...@nostrum.com>> Date: 12 juillet 2019 à 17:51:56 UTC+2 Destinataire: IETF WG Chairs mailto:wgcha...@ietf.org>> Objet: New datatracker featu

[6tisch] Tentative Agenda for IETF 105

Dear all: We posted the tentative agenda at https://datatracker.ietf.org/doc/agenda-105-6tisch/ I understand that all the presenter will be showing up person, so there is no speaker request to be done to meetecho. Please check the agenda whether you have the speaking position you expected and c

Re: [6tisch] TSCH and CCM security proofs

Many thanks Tero. Do you have an intention to add text like this in a draft or in annex of a draft? All the best, Pascal > -Original Message- > From: 6tisch <6tisch-boun...@ietf.org> On Behalf Of Tero Kivinen > Sent: mercredi 10 juillet 2019 23:47 > To: 6tisch@ietf.org > Subject: [6ti

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

Hello Tengfei I think you missed my points >The text was not expected to become normative as is; obviously the usual > ways apply like time out if some but not all beacons are received and sync to > the best. > Yes, I agree with what you said, I replied with a wrong typing word. What I

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

Hello Tengfei tions address is correct. Thanks! “ During this step, the pledge MAY synchronize to any EB it receives from the network it wishes to join. “ In TSCH, time creates an event horizon whereby one only hears transmissions that start during guard time around the scheduled Rx time

Re: [6tisch] call for review: draft-ietf-6tisch-msf-04

Hello Tengfei Many thanks for this update : ) Please find some comments below “ To ensure there is enough bandwidth available on the minimal cell, a node implementing MSF SHOULD enforce some rules for limiting the traffic of broadcast frames. For example, a Trickle Timer defined in

Re: [6tisch] [6lo] ND cache entries creation on first-hop routers

n E Carpenter a > écrit : > > On 03-Jul-19 20:13, Pascal Thubert (pthubert) wrote: > > ... >> I'm baffled that the reactive ND is still the official technique for IPv6 >> lookup at 6MAN. > > How can it be otherwise when a node can give itself a new address at

Re: [6tisch] [6lo] ND cache entries creation on first-hop routers

Hello Michael Please see below > > Pascal Thubert (pthubert) wrote: >> 6LoWPAN ND is immune to the remote DOS attacks on the ND cache, the >> ones coming from the outside of the subnet, i.e., from a place that is >> out of touch and virtually nowhere. > >&g

Re: [6tisch] [6lo] ND cache entries creation on first-hop routers

Hi again Lorenzo, First, complexity. Recovering state in the presence of router crashes is complex. * True; so far we have not designed for the case where the router dies and no-one knows. In the fabric models, the router relays to a central mapping system that it can query later. The cas

Re: [6tisch] [6lo] ND cache entries creation on first-hop routers

Hello Jen The routers that Michael is talking about are real routers, deployed in large volumes in the field, e.g., in Smartgrid networks. They are not running ND as RFC 4861/4862 but as RFC 6775/8505, and then operate RPL routing within the ML subnet. It would be great to have a section that d

Re: [6tisch] [6lo] ND cache entries creation on first-hop routers

Hello Michael 6LoWPAN ND is immune to the remote DOS attacks on the ND cache, the ones coming from the outside of the subnet, i.e., from a place that is out of touch and virtually nowhere. This is because in an RFC 6775/8505-only network, there is no reactive operation, a packet coming from the

Re: [6tisch] Opsdir last call review of draft-ietf-6tisch-architecture-22

(pthubert); ops-...@ietf.org Cc : 6tisch@ietf.org; i...@ietf.org; draft-ietf-6tisch-architecture@ietf.org; Eliot Lear (elear); Carlos Pignataro (cpignata) Objet : RE: Opsdir last call review of draft-ietf-6tisch-architecture-22 -邮件原件- 发件人: Pascal Thubert (pthubert) [mailto:pthub

Re: [6tisch] Opsdir last call review of draft-ietf-6tisch-architecture-22

d the 6TiSCH network, a node acquires IPv6 Addresses and register them using 6LoWPAN ND. This guarantees that the addresses are unique and protects the address ownership over the subnet, more in Section 4.2.2. ' Does that work? Pascal > -Original Message- > From

Re: [6tisch] Opsdir last call review of draft-ietf-6tisch-architecture-22

Hello Qin Many thanks for your review and for the important amount of time you obviously spent on our work. This is really appreciated. Please see below: > By looking at high level architecture section, it is hard to create a whole > picture for what this architecture looks like and how these ar

Re: [6tisch] [secdir] secdir review of draft-ietf-6tisch-architecture-21

27 juin 2019 12:48 To: Pascal Thubert (pthubert) Cc: Michael Richardson ; 6tisch@ietf.org; Tero Kivinen Subject: Re: [6tisch] [secdir] secdir review of draft-ietf-6tisch-architecture-21 Pascal, Before the pledge selects a JP, the text from RFC8180 that is relevant seems to be (Section 6.2

Re: [6tisch] [secdir] secdir review of draft-ietf-6tisch-architecture-21

7:49 > To: =?utf-8?B?TWFsacWhYSBWdcSNaW5pxIc=?= > Cc: Pascal Thubert (pthubert) ; 6tisch@ietf.org; Tero > Kivinen > Subject: Re: [6tisch] [secdir] secdir review of > draft-ietf-6tisch-architecture-21 > > > Mališa Vučinić wrote: > >> Mališa Vučinić wr

Re: [6tisch] [secdir] secdir review of draft-ietf-6tisch-architecture-21

Hello Malisa > >> Instead, as with traditional TSCH, the joined node can obtain its > >> time information from its time source neighbor, i.e. RPL preferred > >> parent, by triggering an exchange of link-layer frames with L2 > >> security features enabled. The MSF draft already mandates that the >

Re: [6tisch] [secdir] secdir review of draft-ietf-6tisch-architecture-21

al-security-11 that is rather > vague. Yes : ) I'm working on high level text in archie, and will propose it to you and Tero. I'll be happy that you refer to it and refine it in minimal-security. All the best Pascal > Mališa > > > On 25 Jun 2019, at 09:29, Pascal Thubert

[6tisch] FW: [secdir] secdir review of draft-ietf-6tisch-architecture-21

indicate that the JRC should be aware of the network ASN to enable the protection that Tero is discussing below, does it? All the best, Pascal > -Original Message- > From: David Mandelberg > Sent: mardi 25 juin 2019 02:31 > To: Tero Kivinen ; Pascal Thubert (pthubert)

[6tisch] 6TiSCH @ IETF 105: call for agenda items

Dear 6TiSCHers, The final agenda for IETF 105 has been published at: https://datatracker.ietf.org/meeting/105/agenda.html. Keep this link, it's always useful with a number of pointers to meeting needful things. Also consider the IETF application for your smartphone... So 6TiSCH will be mee

Re: [6tisch] I-D Action: draft-ietf-6tisch-architecture-22.txt

This version addresses comments by Andy Malis for RTG DIR and David Mandelberg for SEC DIR. A major item was and may still be the amount of non-WG-docs references. We also touched the security section to inherit from DetNet. All the best, Pascal > -Original Message- > From: 6tisch <6tis

Re: [6tisch] RtgDir review: draft-ietf-6tisch-architecture-21.txt

Hello Andrew Please see below Le 24 juin 2019 à 14:40, Andrew G. Malis mailto:agma...@gmail.com>> a écrit : Pascal, On Mon, Jun 24, 2019 at 4:24 AM Pascal Thubert (pthubert) mailto:pthub...@cisco.com>> wrote: Hello Andrew: Many thanks for your in-depth review. Please see belo

Re: [6tisch] RtgDir review: draft-ietf-6tisch-architecture-21.txt

Hello Andrew: Many thanks for your in-depth review. Please see below: > The primary editor of this draft is also active in the DetNet working group, > and leverages the work being done there to support the work in this draft. > The draft does reference some DetNet technologies that have not

Re: [6tisch] RtgDir review: draft-ietf-6tisch-architecture-21.txt

Hello Andrew Many thanks for the huge investment of time you spent on our technology. I hope you found the context of interest. Gory provided a similar feedback and I published 21 to address the specific point of references. Some were removed, some are now WG docs that were not, and the langua

Re: [6tisch] RtgDir review: draft-ietf-6tisch-architecture-21.txt

Hello Andrew: This is another change with Gorry’s review. The spec was intended to follow the path of the DetNet architecture as ses track but we’ll follow the A-Ds and the message was to shoot for informational. So we just changed for it. Regards, Pascal Le 22 juin 2019 à 18:17, Andrew G. M

  1   2   3   4   5   6   >