Re: [netmod] tree diagram guidelines

"Mehmet Ersue" <mersue@gmail.com> Thu, 16 November 2017 03:04 UTC

Return-Path: <mersue@gmail.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640B5129407 for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 19:04:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ug-omgIbdMMm for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 19:04:18 -0800 (PST)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (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 19CC8126CC4 for <netmod@ietf.org>; Wed, 15 Nov 2017 19:04:18 -0800 (PST)
Received: by mail-pg0-x22f.google.com with SMTP id 4so10639339pge.1 for <netmod@ietf.org>; Wed, 15 Nov 2017 19:04:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=an7AtvV2B1iF8Nyjsgi+C2mF7WqTDvOyFxAFqKR4AQw=; b=o9h3d16bmFMKBO4TF1PjUM4E5Qnu5dnR8A5/Fg4kubWd7JbKVQEZb4H0LXT37e1hNI 7dyIAIHjDLekyb3CeS1i0Tnwh/dy26DohXk9dBND8hCIu4VtAsGySHTmkljR+Mjqk6Yq 45VJMmAfkD2lUJ+yyCmhcpgbw9vsg6w0AUQs4E2cMabxD6hejiuWVgzn9Un2GJ4fRysY YPLJv/m0cvBLC66t10sLY2S0loiJ4MBaVeOma+umR0MXXMtjH33P8j5CYECUkJYTeQy8 HMbvlqFjIq7Uvsf1UJEt7zWC+VB/oNOh9+KcZFkJKSnYrSVtOx4r3kfOeYXCjPOJvA4H G3Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:content-language :thread-index; bh=an7AtvV2B1iF8Nyjsgi+C2mF7WqTDvOyFxAFqKR4AQw=; b=thICRloNfa0tupVS4cGGoTVHQjMqHtivYqkm6ELK4fe+W8qx4j7mcOYIXii0XPSh4a GIceVjgWvEDUxXzR8NPbDX2xyxrW8gZrfocgJD9rltbW7Qy2r4ggLABVA2j+UchEzzLh h6B9QIlkSaIzyKgOfTAOYf20bBWqZJUONZY0C4tyZkDAG7+RffHVBQsyhqizc+w17dO7 wMVISLKhvFV73vnwNfPGJSwtk6fNsnchZ235dvzbU7qVcBUR/3EzFlphYxoyPd4R/2xg skFRJfk3RammumKbCFSl/o/E1sReTxHWaoxz9P/7g9oqeyt8QG/1/YnZRE4IK4OajECa qrbw==
X-Gm-Message-State: AJaThX6YiuT8DMHb8Ic2pCkEpM6u06y/E1dgOYn/HUr90OSC394EilGR eExtEyAZ/4aX19uFMnqoBBA=
X-Google-Smtp-Source: AGs4zMYWnDcXSU7EfiAQ3luPSho11AXRO59wBOx2ymKseUJ8mtd3g456yJkhbUquzpDpSmLfryE6pw==
X-Received: by 10.99.124.88 with SMTP id l24mr210483pgn.355.1510801457561; Wed, 15 Nov 2017 19:04:17 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:67c:1232:144:6d1f:df87:592f:459b]) by smtp.gmail.com with ESMTPSA id d2sm122282pfe.164.2017.11.15.19.04.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 19:04:17 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Mahesh Jethanandani'" <mjethanandani@gmail.com>, "'Robert Wilton'" <rwilton@cisco.com>
Cc: <netmod@ietf.org>
References: <20171115.101454.1576716701146734257.mbj@tail-f.com> <bb0f2cf8-ca46-21af-02cd-79970a08db7e@cisco.com> <0696749C-0E80-40CC-9905-BD8187CB6D78@gmail.com>
In-Reply-To: <0696749C-0E80-40CC-9905-BD8187CB6D78@gmail.com>
Date: Thu, 16 Nov 2017 11:04:17 +0800
Message-ID: <014a01d35e87$98797950$c96c6bf0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: de
Thread-Index: AQGxefq6yqyvOLF6jhxyeqpBlh8GFwHgxCcMAmPZNyujN/VQ8A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/kPssiuzGC5oGCX6Z6tbOnjYpf-A>
Subject: Re: [netmod] tree diagram guidelines
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 03:04:20 -0000

The Wiki is useful as a starting point providing a collection of pointers to guideline RFCs and the bis-revisions in development.

Cheers,
Mehmet

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Mahesh
> Jethanandani
> Sent: Thursday, November 16, 2017 7:39 AM
> To: Robert Wilton <rwilton@cisco.com>
> Cc: netmod@ietf.org
> Subject: Re: [netmod] tree diagram guidelines
> 
> Other SDOs can and follow the work in IETF through the RFCs we publish.
> They do not follow wiki’s, unless the document itself says, “here are the
> guidelines, but if you are looking for the latest, go to this wiki”. I therefore
> would support the proposal outlined below. It gives the SDO a stable point of
> reference with a document, which gets updated occasionally, but also allows
> them to peak at what is coming down the pipeline.
> 
> Thanks.
> 
> > On Nov 15, 2017, at 6:53 PM, Robert Wilton <rwilton@cisco.com> wrote:
> >
> > I liked the suggestion from Chris Hopps:
> >
> > I think that it was along the lines of ...
> >
> > The RFC contains a reference at the top that states that updates to the
> guidelines is available on a wiki at ....
> >
> > Every few years the guidelines on the wiki can be folded into a latest
> version of the guidelines draft.
> >
> > 6087bis looks to be 3.5 years old.  Should folks, e.g. at BBF,, IEEE, or MEF be
> using the latest draft guidelines, or should then use the published RFC until
> 6087bis is actually republshed?
> >
> > Thanks,
> > Rob
> >
> >
> > On 15/11/2017 10:14, Martin Bjorklund wrote:
> >> Hi,
> >>
> >> There was a proposal in the meeting today to have the guidelines for
> >> tree diagrams in a wiki, instead of having them in 6087bis or in the
> >> tree diagram document.
> >>
> >> Was the proposal really to have a wiki for just the tree guidelines,
> >> or was the proposal to withdraw 6087bis from the process and instead
> >> publish all guidelines as a wiki?
> >>
> >> If it is the former, is it really worth it?
> >>
> >> Advantages with a wiki:
> >>
> >>   +  It can be updated more easily
> >>
> >> Some drawbacks:
> >>
> >>   -  It can be updated more easily
> >>      (meaning they are less stable)
> >>
> >>   -  Wikis tend to not be alive after some time, and are not that
> >>      easy to find.  Just try to find the various YANG-related wikis
> >>      we've tried to maintain over the years.
> >>
> >>   -  Links in RFCs also have problems.  Sites are re-orginized etc.
> >>      As an example, the link to the security guidelines template in
> >>      RFC 6087 doesn't work anymore.
> >>
> >>   -  People that are looking for a stable reference will have problems
> >>      (I think Rob mentioned that IEEE still refer to RFC 6087 (which
> >>      is understandable; that's the published version).
> >>
> >>   -  Who maintains the Wiki, and what are the rules for updating it?
> >>
> >>
> >> I suggest we have the tree-related guidelines (actually just a few
> >> sentences) in the tree draft, and since 6087bis already refers to
> >> this document it is not a big problem that guidelines are spread out
> >> over several documents that are difficult to find.
> >>
> >>
> >>
> >> /martin
> >>
> >> _______________________________________________
> >> netmod mailing list
> >> netmod@ietf.org
> >> https://www.ietf.org/mailman/listinfo/netmod
> >> .
> >>
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod