Benjamin Kaduk has entered the following ballot position for
draft-ietf-6tisch-architecture-25: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
On Thu, Aug 22, 2019 at 01:23:04PM +, Pascal Thubert (pthubert) wrote:
> Hello Benjamin:
>
> Many thanks for your in depth review of the draft, this is really appreciated.
>
> Please see below:
> > --
> > DISCUSS:
> >
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
Hi All,
For the current version (06) of MSF, we defined the 6P Timeout as the
result of following equation:
6PTIMEOUT = ((2^MAXBE)-1)*MAXRETRIES*SLOTFRAME_LENGTH
o MAXBE is the maximum backoff exponent used
o MAXRETRIES is the maximum retransmission times
o SLOTFRAME_LENGTH
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
Hi All,
As discussed in IETF 105, we are going to support adapting downstream
traffic.
And now this feature is added in draft-ietf-6tisch-msf-06 published one
weeks ago.
Some main changes related to this feature are:
1. After joined the network and got Rank, the node will only add one Tx
Hi all,
As we discussed in IETF 105, we may need some way to monitor the candidate
cells to schedule before adding them.
Hence the following paragraph is added in version 06:
As a consequence of randomly cell selection, there is a non-zero
chance that nodes in the vicinity installed cells
Hi Pascal,
The two issues mentioned in the IETF 105 meeting are
- Rules for CellList
- Downward traffic adaptation
Those two issues are resolved in new version published msf-06.
I will create threads for those issues to clear how they are resolved.
Thanks for reminder!
Tengfei
On Fri,
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 : )
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
: )
I used the heavy weaponry in -25; madi minimal a normative reference and added:
"
6.7. Deeper Considerations
The reader is encouraged to review the security section of
[I-D.ietf-6tisch-minimal-security], which discusses 6TiSCH security
issues in more details.
"
Works?
Pascal
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>
12 matches
Mail list logo