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

Suresh Krishnan <suresh.krishnan@gmail.com> Thu, 08 August 2019 14:01 UTC

Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC6B120044; Thu, 8 Aug 2019 07:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wBMNZhPexuh0; Thu, 8 Aug 2019 07:01:03 -0700 (PDT)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55548120052; Thu, 8 Aug 2019 07:01:03 -0700 (PDT)
Received: by mail-vs1-xe2d.google.com with SMTP id y16so63047644vsc.3; Thu, 08 Aug 2019 07:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qfosRATsukLGVk4h3EOGjf4T5TMAfuaj32kfZjZa4U4=; b=cT/X+ZoMY3M/IOobRJvl9l+lR0X8rIL5BWupN7BL64TpC5b5gSbpmR4B+mN87a6948 niGfzb+IJhT/FnjwP+9oQaqlWU+S15FyPdzPvm8QnXf7RVMYXO0mI8NBmFUtjVUpYVjB cHf0rO/xUDItZZ0i3e5dpWPzKnyJObabwiZo9lew8FpwGw/JzABSeLMqe1rUrW5+kVDH ZmwONbsBCmpVbyIWooxSA4fFCoPP8XbT2Syx1I0HcUZ5HSEU2T/zQ4QY7KauP0f9M902 Pi9gE89yCnuvOgPzX8q03mmFzb5vzyMHwS3ayvNQoc4lEM8srwSctTIFMG9ehsvCZKRj 4DIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qfosRATsukLGVk4h3EOGjf4T5TMAfuaj32kfZjZa4U4=; b=iTaLwqDbVHP9xyfcTbhdbJcG/zLUrFIZpt4mwub9PDLs9s/cNWGS21vpGMP23zg3eG mOb7oLFWAE+96X+H/u2ptUwIRjE7KjTqm85NwZ6wDSQq0dKz1D2KFGjljByRGYbXbQQ2 sJenMrxadzExtVaG0+GkJWiiM59RhdmZVCcmj5YTX8UKSturwUoMGwUjsYDJQDWwfar4 MFEhl0bYKXRVujTgDUOjlkfUTCoXsxHnA3GbOW8TyjOG3o0V5HcNlzpnaGWIrsgzCNDa bYaUQ0tQhoRBr1oY5kC8S+h2Lz5E4B/R4ps2K08KQavo1hL6yRDkMXjQRxkOXB7NCArh uG9g==
X-Gm-Message-State: APjAAAW1mTabqwzUTfJqJbg86O9go1nNj2T1Ly6hqaKU8I2DkzTjExqg 1ivraWbnfe7DPlc8o36woOOJuGcvNAb1P2sAC+E=
X-Google-Smtp-Source: APXvYqxttZRdIf0uwoie1C+k7qr0kWOxCinYZaS4Rhz3os4LCw9P00XnAP58y10twzI2jObEeANKGl1qaDP/ZFyc/wg=
X-Received: by 2002:a67:1281:: with SMTP id 123mr9805357vss.10.1565272862256; Thu, 08 Aug 2019 07:01:02 -0700 (PDT)
MIME-Version: 1.0
References: <156519288057.8345.12430078423880669840.idtracker@ietfa.amsl.com> <F3D6850F-3223-4A25-A9B3-107D09638544@cisco.com> <D465F896-D8E9-4723-AB38-0E7863A59E35@kuehlewind.net> <7ABEDEAB-9C67-491E-BC14-197C4EF1F12E@cisco.com> <7DF936ED-24E7-40FC-9BB7-8DC411BA83C1@kuehlewind.net>
In-Reply-To: <7DF936ED-24E7-40FC-9BB7-8DC411BA83C1@kuehlewind.net>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Thu, 08 Aug 2019 10:00:49 -0400
Message-ID: <CA+MHpBrZ7HF+jpEVZfDxZY2gMChBe0SAnH3bW4PqHekjov9GYQ@mail.gmail.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: Pascal Thubert <pthubert@cisco.com>, Shwetha Bhandari <shwetha.bhandari@gmail.com>, "6tisch@ietf.org" <6tisch@ietf.org>, "6tisch-chairs@ietf.org" <6tisch-chairs@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-6tisch-architecture@ietf.org" <draft-ietf-6tisch-architecture@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ee77c1058f9b7c0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/EZxa_qVWl1KPi8FZo0xuF2O8q6I>
Subject: Re: [6tisch] Mirja Kühlewind's Discuss on draft-ietf-6tisch-architecture-24: (with DISCUSS and COMMENT)
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 14:01:06 -0000

Hi Mirja,

On Thu, Aug 8, 2019, 6:29 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote:

> Hi Pascal,
>
> See below.
>
> > On 7. Aug 2019, at 20:31, Pascal Thubert (pthubert) <pthubert@cisco.com>
> wrote:
> >
> > Hello Mirja
> >
> > It certainly does not hurt to have a second look at how the split was
> done and why.
> >
> > With one exception - the DetNet Architecture - the references fall in
> the category of solutions which is a level below this spec in the design
> cascade.
> >
> > They explain how things are done when this spec tries to limit at what
> gets done and tries to be complete at it. We can point on the solution
> specs because we only publish once the work is mostly done as opposed to a
> as a preamble to the work like in the case of DetNet. Then again that was a
> conscious decision be the group which is more of an integrator than a
> creator.
> >
> > From that perspective only the DetNet Architecture would be normative,
> the other specs playing at a different level and not needed for
> understanding things at Architecture level.
> >
> > OTOH it would be grand for this spec to reference RFCs as opposed to
> drafts. That would help the reader. But then there are many solution draft
> and we could keep building new ones forever.
> >
> > I’m unsure what you mean by strongly wrt the fragment drafts. They have
> a purpose and the Architecture describes that purpose. Since it has an
> Architecture impact with per packet l’avales and stuff we had to explain
> it. Did we go too far into explaining the solution?
>
> Yes, I had the feeling that is went too much into details a couple of
> times. However, as I said, I didn’t read the document in depth and
> therefore can’t give strong advise.
>
> @Suresh: Can you maybe have another look at the reference. If you are okay
> with the current approach, I’m happy to clear my discuss. Mainly wanted to
> double-check!
>

I was fine with the current approach to references but I do see your point.
I will try to see if I can propose something to simplify this.

Thanks
Suresh