Re: [6lo] Roman Danyliw's Discuss on draft-ietf-6lo-deadline-time-04: (with DISCUSS and COMMENT)

Charlie Perkins <charles.perkins@earthlink.net> Fri, 31 May 2019 21:15 UTC

Return-Path: <charles.perkins@earthlink.net>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F047120072; Fri, 31 May 2019 14:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.115
X-Spam-Level:
X-Spam-Status: No, score=-3.115 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.415, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ui1ENJBSzO00; Fri, 31 May 2019 14:15:33 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E89D1200F9; Fri, 31 May 2019 14:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1559337333; bh=+XqhIzHUz167YWXAlvyp5kT+U6nF/jhYAvLT Z+mCvvw=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:Content-Language:X-ELNK-Trace: X-Originating-IP; b=S79+4laj3HyL/C3wq9GsUXjDIy34losmgvV6hUrHfD/iS8 aMpfDA1Uz8Dy1Va5AxQmyY1ClA5ukK9UN3k/BeR5abo+2QsRrntTDgNF1mkcHrlUeRw iy30knmlHVtqz6usJAmm+H2Jdc9XC8zhudqriKsTsMXqedR0FPlfWk5fB9T1WhivWsy 1Or1Yjrp6orjFzgdsxDlfsBLUGEcFnhRYuOH9pOGL3OQZHsn6l6DGqi6rC+mXTLPAgQ 0MYsVH3WmLULdkPTslMleyheWNFmIzuEd9DRF9fXncSTiOek3RLZwnxN/uE3BaYHmdp a8cH4FCozNJ3k2pXWZpMCS0ghHaA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=J5uwx9IXnI1MPxuOhOfsl8mvJUm0f5+5XsScrznZSkJGAc88UzIdfm4TDN+cS1D9u3OSTjeCADnbONNl5PU6YQIPW14dJJWtJG0U3VtP/kMgH1Wwdqi77zfOhS7rugQkJULQy9NuDqaXF5xox+cMXSWvDSO5nrReIHhcXXHOU/SDh8fxta1ODgKzokc3m+LudRC4mdiQeHq4OsDmNeP9y5dv49vJX/7Jda08j0m9Fzt/Ea5p4czNtGwzR/smBi/utmxKAaMgbNmnjZ6UGuyEpRCC6xdrvW5vrIcm95z6TPlJK0dfXGpiZBWUozP1ukSiho2GlW3f0gkYBjHXVQbJ1w==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1hWos7-0006n6-Mj; Fri, 31 May 2019 17:15:31 -0400
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: draft-ietf-6lo-deadline-time@ietf.org, Samita Chakrabarti <samitac.ietf@gmail.com>, Shwetha Bhandari <shwethab@cisco.com>, 6lo-chairs@ietf.org, 6lo@ietf.org
References: <155801295610.19776.17352306388780302849.idtracker@ietfa.amsl.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <aaf94f20-fdde-ff3c-aacb-1332e2ae080a@earthlink.net>
Date: Fri, 31 May 2019 14:15:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <155801295610.19776.17352306388780302849.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c9509b3df8f58a32346e4eb128238c9e78e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/kO-RuFQdipUlP1eb88NcWeZvekI>
Subject: Re: [6lo] Roman Danyliw's Discuss on draft-ietf-6lo-deadline-time-04: (with DISCUSS and COMMENT)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2019 21:15:35 -0000

Hello Roman,

Please see below for some follow-up...

On 5/16/2019 6:22 AM, Roman Danyliw via Datatracker wrote:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-6lo-deadline-time-04: Discuss
>
> ...
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-6lo-deadline-time/
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> I support Magnus’s DISCUSS #1 (and perhaps we are noting the same thing)
>
> The current Security Considerations text needs explicit discussion of the
> impact of the deadline being manipulated.


I agree with this.  Please also refer to my response to Magnus's 
observation and DISCUSS.


>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> (1) I also support Barry’s DISCUSS on the need to discuss what happens to a
> network where all senders have short deadlines

I also agree with this as noted in my response to Barry's observation 
and DISCUSS.  We will fashion appropriate text, and my guess is that it 
would go into the Security Considerations.  Do you think that is the 
right place?


>
> (2) Section 5.  Per the description of the D flag, how would a forwarding
> device “suspect that a downstream node might find [a packet] useful”?

I don't have the answer to that question.  I could imagine that 
intermediate devices are configured with traffic descriptors that cause 
a match to the "Forward_IF_D=0" behavior.  We could make a suggestion, 
but then avoid a normative condition for this behavior by specifying 
that the configuration details are out of scope for this document.  
Would that be O.K.?


>
> (3) Section 6.  Is there normative language about the behavior of forwarding
> entities when encountering the Deadline header in this section?  If not, I’d
> recommend adding explicit text to that effect.

This has been discussed in other emails as well.  It is possible to 
mandate that the Deadline header SHOULD NOT cause pre-emption. I think 
such mandates are not enforceable, but would anyway serve as guidance 
for implementation.


>
> (4) Editorial nits:
> ** Section 4.  Typo.  s/the the/the/


Thanks much for your review!

Regards,
Charlie P.


>
>