Re: Rights in early RFCs

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Sat, 15 June 2019 10:48 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43346120020 for <ietf@ietfa.amsl.com>; Sat, 15 Jun 2019 03:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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] 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 Tr1axQfmh4bB for <ietf@ietfa.amsl.com>; Sat, 15 Jun 2019 03:48:45 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 42D08120019 for <ietf@ietf.org>; Sat, 15 Jun 2019 03:48:45 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id e8so4075881otl.7 for <ietf@ietf.org>; Sat, 15 Jun 2019 03:48:45 -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=w6dkQ+NvdqfFKclB6/BzF53IYhPux+3Uv2Mqi+3WpMM=; b=CbapUJoezq9jQiShowxIGcRUZRBwONJxWF7LiGWlxjUR2C2fkHxT8agRpLW737gdLf 1FIVuhYdOS1YsyVFM1VAWRS8/CxL81KvjX647/I/lnELyPnK1c+Zq8+Zr7l/P/hKp89J ROWG0Umd3DdMYW+pvhnr9D+ZVPYKYWcEHhdgf54XaE62dQakplAoRT/7YL/meUxl+1WO dLaI/doL6LpfzyCV7nCw0vJ/2RuqwTe7TE+6qa8id1uGnQ7ZDjootLGZG3LPk+1DkKCG EQnYyDXFXb6t8GOYMkrrqqBG5uh68x/mSu217cWxNMvTyeaBCpTL2NmCo2QfZdS7ZPUS z3Xg==
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=w6dkQ+NvdqfFKclB6/BzF53IYhPux+3Uv2Mqi+3WpMM=; b=g3uVu0r9K1kgqAFGCeHl6ZGue+ihsnOs1X0HuYCj74tImWMpjLl8wC/cjhRNjXEfDv kY+PhtqlNAQjRTcKhIggFxmIPRUvKmv4cZFQTXRMo+h4p8DCiHvjhFteEboPk4rXsELD zeLB5RZfU5ZvN+eRmpYnKRBtdeZUreI05UTKPenTUdz8Z5QEKqN/qTSqbwqSCSJMGP/+ tVM/zJOfkkbK4KKpp892wz5tevkWJGZYNyaPGVeD0rjLXh/UZOIu7D81+gCoFCAtdIKW /q3sIJA9mMA2uIH8D1ZeaISM90Vc1NyyEN6JcTpxcWA+uOkPNguPABSM1b5ErbkAQH5R ozmA==
X-Gm-Message-State: APjAAAWHu6UjaEmrUjPqRhGGvf/lmbNT9EFAE0ZVfaJPWd93T6WBaMau c/VufVyHE1FMKi3rSRly0tMopm9rkiJVpoc8ApiTi4UO
X-Google-Smtp-Source: APXvYqzIZxHsc2TtjV/3VA9T/V/WOS+lJozQwypnbFXOjYCMFIB1vhqlSaTRZJ5cx14TuW6w2o6+6+GBigA9EGVLVcY=
X-Received: by 2002:a9d:76ce:: with SMTP id p14mr383810otl.342.1560595724168; Sat, 15 Jun 2019 03:48:44 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.OSX.2.21.9999.1906141728410.11884@ary.qy> <A89856255D980EBDE462508F@PSB> <F1C084A6-BB9E-4AFB-AB31-C547FD0FEEE4@sobco.com> <A3DE5329-2B88-4FB4-A1D5-E85EEC409A08@vpnc.org>
In-Reply-To: <A3DE5329-2B88-4FB4-A1D5-E85EEC409A08@vpnc.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Sat, 15 Jun 2019 06:48:20 -0400
Message-ID: <CAHbuEH5qcpPmUa7TnY6UhsCJCGMYtPAW=F5uQOWrnZYVLrFmtA@mail.gmail.com>
Subject: Re: Rights in early RFCs
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: Scott Bradner <sob@sobco.com>, IETF general list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c6f18a058b5a81c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iSM0yH9_RbgbR52kEjRns7c_Z-E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jun 2019 10:48:47 -0000

I'll add to Paul's description.  Within the request, for one document, they
wish to make a profile.  Normally, that's fine.  Except that they want to
change keywords in directions that they should not be changed in a
profile.  For instance changing a MUST to a SHOULD or even a MUST NOT.
This obviously results in the profile not being in compliance with the
referenced document and therefore not interoperable.

I went through this with another SDO and was able to work through it.  I am
not finding the documentation to support the bounds of profiles though to
determine if that sites with the response from the Trust or elsewhere.
I'll keep looking, but if someone has the answer, that would be very
helpful.

Thank you,
Kathleen

On Fri, Jun 14, 2019 at 7:44 PM Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On 14 Jun 2019, at 16:14, Scott Bradner wrote:
>
> >> On Jun 14, 2019, at 7:06 PM, John C Klensin <john-ietf@jck.com>
> >> wrote:
> >>
> >> There were several later rounds of conversations about the
> >> general topic on which Scott Bradber would be m8ch more expert
> >> than I am, but I'd be surprised if the answer from him would be
> >> significantly different from the above.
> >
> > It is not
> >
> > but I do have a question for John Levine - what is the context of your
> > question?
> >
> > republish? produce a revision? ???
>
> Oddly, I can answer that one. Some people quite outside the IETF want to
> publish a spec for how to do $foo over the Internet. Their spec quotes
> small parts of various RFCs to make the requirements clear for the
> vendors who will implement $foo because those vendors do not normally
> use IETF standards. They were unsuccessful in finding how to get
> permission to quote from RFCs, and by circuitous route got to me. I
> passed them along to the IETF Trust, and that's where John's message
> originates. (Side-note: they didn't know who Jon Postel was or how to
> reach him to ask about getting the right to quote RFC 768. I had to
> break that news to them...)
>
> --Paul Hoffman
>
>

-- 

Best regards,
Kathleen