IETF Logo Mail Archive

Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Tue, 06 July 2021 17:33 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
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 97CD63A2F4D for <netmod@ietfa.amsl.com>; Tue, 6 Jul 2021 10:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.234
X-Spam-Level:
X-Spam-Status: No, score=-2.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IxkTdLbTMVZF for <netmod@ietfa.amsl.com>; Tue, 6 Jul 2021 10:33:18 -0700 (PDT)
Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) (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 ED3663A2F4B for <netmod@ietf.org>; Tue, 6 Jul 2021 10:33:17 -0700 (PDT)
Received: by mail-pj1-f45.google.com with SMTP id h1-20020a17090a3d01b0290172d33bb8bcso1977740pjc.0 for <netmod@ietf.org>; Tue, 06 Jul 2021 10:33:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CDvZYbIDfFsf6tl/cjtfZH9xmyKaZZ92wJFfninBgXU=; b=LV2AToxzShJLPyMStZELy6RU4o866G/CSdFAEfRSgLkbevMYOs7IjcYUavhV1K3gNY Ztt9IXvBErDejSr1sPTsOcvlOCdsgY6dEDiWUUBgUXM/NZo65jxZ43ytxPinEYu9O5F9 TF0muk/BqcgAde/Rz9YOQOTASFWoB770invuWiLMgbrSGu2+LshgshrXxtmMed/BPQ6w M1dnsZ/6cF8C08GFVB3mnV/lPW/udLR/+Usg/f5Z+Naqaay1u/xooheRC20nveRUjkAt uneLsZH2m+hljWN5YvaaoHIrgwiXykA6jJ4RfgQEQ9U+G0qdcxsG99WVVXdKxVFFDSSg FUqg==
X-Gm-Message-State: AOAM533DHULQyfa3Td+JcaU+FbSfEla6Dn1NqTPxKht0OFhZCF1HJFBd phR891fuEe5XNBnnxQH5IL5tEw==
X-Google-Smtp-Source: ABdhPJwWJE7WE4m/RjziwSP256j2ySDYI3W+dwmx83dDM6nx/C+vDdMolFnsQBJzAYBT1lS/VNhKzQ==
X-Received: by 2002:a17:90b:1209:: with SMTP id gl9mr1525633pjb.213.1625592797348; Tue, 06 Jul 2021 10:33:17 -0700 (PDT)
Received: from ?IPv6:2601:646:9300:791:b1c9:b90a:8e13:d96f? ([2601:646:9300:791:b1c9:b90a:8e13:d96f]) by smtp.gmail.com with ESMTPSA id x4sm19079282pgr.40.2021.07.06.10.33.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Jul 2021 10:33:17 -0700 (PDT)
To: tom petch <ietfc@btconnect.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "netmod@ietf.org" <netmod@ietf.org>, "anima@ietf.org" <anima@ietf.org>
References: <AM7PR07MB62485680255CC66AC5691924A01B9@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <26c27178-7dbd-de29-b99f-10a969257769@alumni.stanford.edu>
Date: Tue, 06 Jul 2021 10:33:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <AM7PR07MB62485680255CC66AC5691924A01B9@AM7PR07MB6248.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/bmOPgkSU1s6u_JLe9dm8qdap-MU>
Subject: Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Jul 2021 17:33:23 -0000

Hi -

> From: netmod <netmod-bounces@ietf.org> on behalf of Michael Richardson <mcr+ietf@sandelman.ca>
> Sent: 05 July 2021 21:40
> 
> Randy Presuhn <randy_presuhn@alumni.stanford.edu> wrote:
>      > In ltru the I-Ds contained both material for publication
>      > in the RFC as well as a *massive* amount of material for
>      > population of the IANA language tag registry.  We needed
>      > it in I-D form for review during development, but wanted to
>      > remove all temptation to use the RFC instead of the IANA
>      > registry.
> 
>      > All it took was a word of instruction to the RFC editor
>      > to delete the many many many pages of registry content
>      > upon publication.  Worked fine.
> 
>      > In this case, just tell the RFC editor to delete the
>      > IANA-maintained module.
> 
> I think you mean, the RFC-maintained module :-)
> How do we keep the YANG catalog from latching onto it.

No.  The to-be-maintainted-by-IANA module appearing in an I-D would
never appear in the published RFC text.

Randy

v2.23.0 | Report a Bug | By Email