IETF Logo Mail Archive

Re: [I2nsf] [yang-doctors] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC

"Acee Lindem (acee)" <acee@cisco.com> Wed, 10 April 2019 11:36 UTC

Return-Path: <acee@cisco.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76FA512029F; Wed, 10 Apr 2019 04:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=AGFwwpWI; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Nwl4FPSV
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 NZ68tcK-SMUN; Wed, 10 Apr 2019 04:36:21 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 148CB120291; Wed, 10 Apr 2019 04:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2390; q=dns/txt; s=iport; t=1554896181; x=1556105781; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QiSDnWEv5EEzZ6owsgN9ylzX37pTS954dtmaM510K4o=; b=AGFwwpWI5EuX17WtE2OvMMAuZPaDMFqG9XTIsTFyrxHhi+fHAp5QKu4q 0Qj7AUukGvTD8vNTEQRhk9+fkVKSjcueZ/4/sZXXffieY8ynAh+VMza0L 8vGNqpGiYbdRFZSbnrxZBDiHy9oGMVc2FkSa3Igb9HZYuGJ62jWLweCdO k=;
IronPort-PHdr: 9a23:N6/iGhYrgZvT9pPeA0C/daj/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20QKbRp3VvvRDjeee87vtX2AN+96giDgDa9QNHwQAld1QmgUhBMCfDkiuJfXnYgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B5AAAS1K1c/5ldJa1iAxkBAQEBAQEBAQEBAQEHAQEBAQEBgVQBAQEBAQELAYE9JCwDaFQgBAsnCoQEg0cDjx6CV5cYglIDVA4BARgLCYRAAheFUSI3Bg0BAQMBAQkBAgECbRwMhUsBAQEDAQEhEQwBASwLAQ0CAgEIDgIIAgIfBwICAhkMCxUQAgQBDQWDIgGBXQMVAQ6hMAKKFHGBL4J5AQEFhQMYggwDBQWBBiUBi0YXgX+BEScfgh4uPoJhAQGBeAomgkMxggQijRiYE2IJApQFGoIGkl6LVoEakmQCBAIEBQIOAQEFgWUigVZwFTsqAYJBggo3gzgzhGGFP3KBKI4lAYEfAQE
X-IronPort-AV: E=Sophos;i="5.60,332,1549929600"; d="scan'208";a="543877386"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Apr 2019 11:36:19 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x3ABaJ83027007 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Apr 2019 11:36:19 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 10 Apr 2019 06:36:18 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 10 Apr 2019 07:36:17 -0400
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 10 Apr 2019 06:36:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QiSDnWEv5EEzZ6owsgN9ylzX37pTS954dtmaM510K4o=; b=Nwl4FPSVOKywrKM7usSkqh7wCgPxKtBYMxK3RnL83G9bd8j7gFjNF9Hwal96aYZP6RCxw3fzAPw9gCEmfdyi1v8BXCwWKQNYcmkZiu43kEsgLmpwFlm5xVyEMBlVFaIqpcRGsPiJrmKY/ZoZXBBljJEhMrxNmL3BkDOle8F506U=
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com (10.174.112.11) by BN6PR1101MB2273.namprd11.prod.outlook.com (10.174.113.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.16; Wed, 10 Apr 2019 11:36:16 +0000
Received: from BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9105:38a0:c6b:f455]) by BN6PR1101MB2226.namprd11.prod.outlook.com ([fe80::9105:38a0:c6b:f455%7]) with mapi id 15.20.1771.016; Wed, 10 Apr 2019 11:36:16 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Paul Wouters <paul@nohats.ca>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
Thread-Index: AQHU69tX1AVOQiz/7EutscpLYLzlNqYzeeUAgAA8KgCAACIGgIABSpcAgAABAICAAAWmAIAAGU4AgAABwYD//8QQgA==
Date: Wed, 10 Apr 2019 11:36:16 +0000
Message-ID: <2DA48994-C8DB-4CCD-B87F-552AB88F35F4@cisco.com>
References: <420D3E9A-9E3C-4575-9C92-200CAA0B868C@gmail.com> <CABCOCHRf3iGUt9wb3htpDYGJ+pAKErvq8OrozndgELUVKYT4Kg@mail.gmail.com> <80347D5B-C4DB-4F0C-BD73-A927585442BF@gmail.com> <D19CB266-D1D8-429E-A215-6BE866098E90@um.es> <6CC456A8-69B9-4D87-9A29-2DCE65E60EB2@gmail.com> <05E72A30-E28B-487A-A38C-EB7720F5B360@gmail.com> <87k1g2z0nj.fsf@nic.cz> <alpine.LRH.2.21.1904100512290.14618@bofh.nohats.ca> <061a6eba967d6223bbc99febb189d40d7fad21aa.camel@nic.cz> <alpine.LRH.2.21.1904100700080.20947@bofh.nohats.ca> <20190410111047.2s6n5plppk6bhdc4@anna.jacobs.jacobs-university.de>
In-Reply-To: <20190410111047.2s6n5plppk6bhdc4@anna.jacobs.jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [173.38.117.89]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ac7de3f2-39e5-4c6f-f068-08d6bda8be8c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:BN6PR1101MB2273;
x-ms-traffictypediagnostic: BN6PR1101MB2273:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BN6PR1101MB2273F33B6327AEA945CA47E8C22E0@BN6PR1101MB2273.namprd11.prod.outlook.com>
x-forefront-prvs: 00032065B2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39860400002)(136003)(396003)(376002)(366004)(199004)(189003)(110136005)(86362001)(81166006)(11346002)(53936002)(2616005)(105586002)(6116002)(8936002)(476003)(66066001)(54906003)(446003)(3846002)(8676002)(81156014)(83716004)(316002)(106356001)(71200400001)(71190400001)(82746002)(6506007)(5660300002)(76176011)(4326008)(186003)(6512007)(26005)(6246003)(97736004)(102836004)(25786009)(2906002)(6486002)(6306002)(486006)(68736007)(229853002)(478600001)(6436002)(14454004)(305945005)(966005)(14444005)(93886005)(256004)(7736002)(36756003)(33656002)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1101MB2273; H:BN6PR1101MB2226.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: xNC6/IfdUHoeVO95+eaa+GWSg5Jcl6+rQh9Yce1yc2xoQzUO8otrDJuK1gNRByiImgq6izer1XBntM/bPmXekVTIeB6m/5+ZpYYUMEND5ZCZ5FQLXD0uwqFf0HQ9r083Xs59Xd6UGTypo+MdxRocF4zji0X5OTiUA0yhHJkZVPuKpcCEpQSyMuHvTimBDbG+qfGtfQOx7giF7780XSYAJOzUvR1odEB6w8fDd55ZsQGoN65CU3fWLp1xX+rsk56zk9gLw9TWTbHfzl5CVbkH5bs9tD0ghmvLijxOB+CTXIV7z2LEX1tm70Vj0bUExQsy9+GUzbNoQmMAYzVquwSyp8YJ6J18hombUY59RzO5HIOJxTHzOuzAaUM37D9l4Fkst7++zNc3PWl20IfuEVp8wmyOrPARV+D62OIottlNqKc=
Content-Type: text/plain; charset="utf-8"
Content-ID: <066E1BE8E9AB004C817B603FE5551304@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ac7de3f2-39e5-4c6f-f068-08d6bda8be8c
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2019 11:36:16.7175 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1101MB2273
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Ih8GUGSS-vwtJf5eR1BDQ7bEexE>
Subject: Re: [I2nsf] [yang-doctors] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 11:36:24 -0000


On 4/10/19, 7:11 AM, "yang-doctors on behalf of Juergen Schoenwaelder" <yang-doctors-bounces@ietf.org on behalf of j.schoenwaelder@jacobs-university.de> wrote:

    On Wed, Apr 10, 2019 at 07:04:30AM -0400, Paul Wouters wrote:
    > On Wed, 10 Apr 2019, Ladislav Lhotka wrote:
    > 
    > > Not necessarily. If you look, for example, at RFC 7224, it is IANA's
    > > responsibility to keep the registry in sync with the YANG module. No further
    > > effort is required from the WG that prepared the initial revision of the module.
    > 
    > What is "the YANG module" ?
    > 
    > I don't think IANA has any responsibility other than RFCs directing them
    > to update IANA registries. How do you imagine any updates to happen, and
    > how would IANA "sync" this automatically?
    >
    
    There are IANA maintained YANG modules (and before we had YANG there
    were IANA maintained MIB modules). Numbers maintained in registries
    sometimes need to be in machine readable formats and then IANA
    documents procedures to make updates both in their internal registry
    and in an IANA maintained YANG module.

It seems this could all be done with tooling. However, AFAIK, generation of new versions of IANA YANG models had not be implemented yet. 

Thanks,
Acee


    
    /js
    
    -- 
    Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
    Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
    
    _______________________________________________
    yang-doctors mailing list
    yang-doctors@ietf.org
    https://www.ietf.org/mailman/listinfo/yang-doctors

v2.23.0 | Report a Bug | By Email