IETF Logo Mail Archive

Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification

Michel Veillette <Michel.Veillette@trilliant.com> Thu, 13 September 2018 20:42 UTC

Return-Path: <Michel.Veillette@trilliant.com>
X-Original-To: yot@ietfa.amsl.com
Delivered-To: yot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77425130E16 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 13:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.onmicrosoft.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 8G5JUILd-IUS for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 13:42:32 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0703.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::703]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4E3D130E63 for <yot@ietf.org>; Thu, 13 Sep 2018 13:42:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-Trilliant-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=R0KB+kUYjIvzp1crVeJXxbOJ8sEtAdH2T430fSE3WJs=; b=SL81achtHFbxGjALg9KvOule76jr2HADgfuDQHEXAUjxtXvzBSkeMeuiR10Zsu3WrsbBXyRjIbWKoI4dEYdTT9Qh34xEviXVadnVlyrw+yw1s3bJx0bH1Fz9/w7oTli9B1SKIeOAn65ODvMIn3zwvtLqgIcsruiWeioMvrxf6eA=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB3338.namprd06.prod.outlook.com (10.174.243.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.17; Thu, 13 Sep 2018 20:42:29 +0000
Received: from DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8]) by DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8%3]) with mapi id 15.20.1122.019; Thu, 13 Sep 2018 20:42:29 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "yot@ietf.org" <yot@ietf.org>
Thread-Topic: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification
Thread-Index: AQHUShTI49tf+ze05UurFksSWsBc2qTst/jggAEZyQCAAAksAIAA0fCAgAAAdoA=
Date: Thu, 13 Sep 2018 20:42:29 +0000
Message-ID: <DM5PR06MB2777478F6E23ACAF2D54C6919A1A0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <29651.1536700610@localhost> <DM5PR06MB2777C6B37AE975F3DC189F599A1B0@DM5PR06MB2777.namprd06.prod.outlook.com> <20180913.092534.2221140746488750178.mbj@tail-f.com> <20180913075824.vd5ecwvd5wg5t4fv@anna.jacobs.jacobs-university.de> <19841.1536870587@localhost>
In-Reply-To: <19841.1536870587@localhost>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB3338; 6:yIJPHNuJFqzPq/u0fDjoo7M6CZtQ1jrOd4jcsy/tmMWqG3ViPAyPcbK7jIBiwDSXlMQTGlyemd1bUOjYEzeC32rBlt3y+vEq7oDtdS1NVH8f5ZYgdPlw9KQJ6/e8lh3upblJGCr2okqJdldJt1cyOBl7QsJajxFq7ELqXTKiPpQORgYt1iM2MwgGO0jT+I+BTnS+qZJWYRDm/K9xNslTxH++Pb4seZ1+P2s4cwiNZQowaUT5I55jXgLRPwylwXJBMNFmILrBzB1Az59Whghz5IyiD84Z2GK5TMm8R6fms/Se9NtOJ4YIN50tBBWACKpxahK+XT1b9fn9xJAZsiFxh4C+5nmMQazw38JdPmyrWRdsYglRL+czbjDdO8BFQnfrp9uKcvqI/krzWkqB2tyxcK6WSlJ0Vg8CbW8Zph4yFwMSGGkkCjY2gPIrF8ymox7bViD66bv8x0SoC/NFGpAuAw==; 5:6CmylDCJCVV/7O5zxoxFa3/0Ax0p/w41uaCaSiVG+KTwee7ijYcSC0kockfi0uYwaRw9Umeg88dB9/oXwCESG90mf+WhEKSKb96jklaFFS0X83QzcifC4Lsndc5pagWbG3l3runQ+O5jINquZHOICDpORcm+T2PtSYznejUfuFk=; 7:PEKfu4ZiUhZNO+NARnDbF3qdnWxHK40xkgKGSlBSlxlA0jevEfTnyNUN6oDn4/IYdssPsGCy8UUR2SyN09SDdsjzIVzihAxPMJX2MuPSlsktL1IYUoiu2Gs2amvE5RpU/c3a4mB3gIwzuKtFpFOdqYRUIVEOvqOHzxBrU1HR5+sHLKNn7+xWgG14Umt6xyiI9xwQuQa4sSisKAmageI9ALpnE/f2E5g1gT24IgmgREl0mW8lwPygZYks6D/b94li
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 17fe2080-d30b-4e6e-0955-08d619b96c3d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB3338;
x-ms-traffictypediagnostic: DM5PR06MB3338:
x-microsoft-antispam-prvs: <DM5PR06MB3338890AD0CA5CA6D370DB809A1A0@DM5PR06MB3338.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(3231311)(944501410)(52105095)(93006095)(93001095)(3002001)(149027)(150027)(6041310)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(201708071742011)(7699050); SRVR:DM5PR06MB3338; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB3338;
x-forefront-prvs: 07943272E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(366004)(376002)(39850400004)(136003)(13464003)(189003)(199004)(81156014)(3846002)(8936002)(81166006)(99286004)(316002)(5660300001)(110136005)(76176011)(2906002)(7696005)(6246003)(106356001)(186003)(478600001)(14454004)(6116002)(4326008)(68736007)(97736004)(72206003)(2900100001)(93886005)(33656002)(11346002)(6436002)(105586002)(8676002)(229853002)(86362001)(446003)(53546011)(256004)(25786009)(486006)(55016002)(5250100002)(476003)(102836004)(9686003)(66066001)(6506007)(305945005)(53936002)(74316002)(26005)(7736002)(14444005); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB3338; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 9u1MZ7FXIZx0PXq8jGYdbkRsLNykBR8dKrqjwpb8DvxXYPQrXHuzxVQqqhO0qH+lLuTyoV0CNpyzYsVrsx8Oqog8BdxvtBeX2C6Fwtb2dogla8G3PEe0EwWKz98T17ezmUiL4Cr1GZ67aCy8kmC1QwK8GGmwm/L5Lu32i4K81pZA79io5sc0RdUDjo2LekBLRzBJIAstP6B1TnqevCfm5BGltDCyUDWALCn15g8ncq1PvQ3Huvb9EBQa5RdfGYP9As41NuqR6ZPStdbJ1jfZI33HcflNudtz8F3VzwY1DUprN8wcEehvoIrYH1k1umZV4+FXBJhh+YFBLst2iPvqZlW+vFLDTz7VWJ5edg5yS3I=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Trilliant.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 17fe2080-d30b-4e6e-0955-08d619b96c3d
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Sep 2018 20:42:29.3681 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB3338
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/gWvJq0w5gWlkVhI05RLPJRceRAQ>
Subject: Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Yang of Things <yot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yot>, <mailto:yot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yot/>
List-Post: <mailto:yot@ietf.org>
List-Help: <mailto:yot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yot>, <mailto:yot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2018 20:42:36 -0000

Hi Michael

As a first step, the sid.py plugin need to be added to the official pyang github project.
This imply that we need to fully support python 2.x and we need to produce the required stuff (e.g. documentation, ....).

For the python script used by comi.space (i.e. sid-registry.py), we need to find a home for it.
Which github account should be used for it?

Regards,
Michel

-----Original Message-----
From: Yot <yot-bounces@ietf.org> On Behalf Of Michael Richardson
Sent: Thursday, September 13, 2018 4:30 PM
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: yot@ietf.org
Subject: Re: [Yot] [Anima] documenting SID usage in IETF specification (fwd) Michael Richardson: [Anima] documenting SID usage in IETF specification


Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
    >> > It will make sense to optionally add them in the IANA Considerations
    >> > section of each RFC.
    >>
    >> Is the intentation that this will done for *all* YANG modules
    >> published in the IETF, or just for the YANG models from some WGs?

    > The sids are machine generated, no? If so, why can't we make IANA
    > maintain the sids? This way, sids can be created for YANG modules as
    > they are needed and we do not have to cast sids into RFCs just in case
    > they could be needed.

For many modules that are used in another module it make sense not to allocate things.

The problem right now is that the tooling is not yet reliable enough to pass to IANA.  So we need some interim strategy.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email