Re: [i2rs] relationship between "draft-ietf-i2rs-pkt-eca-data-model-00.txt" and "draft-ietf-i2rs-fb-rib-data-model-00"?
"Susan Hares" <shares@ndzh.com> Thu, 30 June 2016 21:53 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF7912B046; Thu, 30 Jun 2016 14:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.739
X-Spam-Level: *
X-Spam-Status: No, score=1.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no 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 IibSJQS4_Fvh; Thu, 30 Jun 2016 14:53:26 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (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 85E9D1288B8; Thu, 30 Jun 2016 14:53:26 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.165.235;
From: Susan Hares <shares@ndzh.com>
To: 'Linda Dunbar' <linda.dunbar@huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F657ED8E6F@dfweml501-mbb> <49ba01d1d2d9$6a616900$3f243b00$@ndzh.com> <4A95BA014132FF49AE685FAB4B9F17F657ED93D0@dfweml501-mbb>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657ED93D0@dfweml501-mbb>
Date: Thu, 30 Jun 2016 17:52:49 -0400
Message-ID: <00ce01d1d319$befba120$3cf2e360$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00CF_01D1D2F8.37EBAED0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHncFAgf84dghdL2BTfsUw/dGlBUAHyHSyaARNDNPmfvx2zMA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/PRRp5JlLn0QE8VSZNxijnhaTY8I>
Cc: i2nsf@ietf.org, i2rs@ietf.org
Subject: Re: [i2rs] relationship between "draft-ietf-i2rs-pkt-eca-data-model-00.txt" and "draft-ietf-i2rs-fb-rib-data-model-00"?
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 21:53:29 -0000
Linda:
The reason for three different yang modules (fb-rib, fb-rib-type,
pkt-eca-policy) is modularity of the work. The
draft-ietf-i2rs-fb-rib-data-model contains two modules (fb-rib-types,
fb-rib), and draft-ietf-i2rs-pkt-eca-policy-data-model contains
pkt-eca-policy. I could put these all in one module if it is more
convenient.
The modularity of the yang modules are to focus :
1) pkt-eca-policy - packet ECA policy
2) Fb-rib-type: on modules definitions for fb-rib
3) fb-rib: operat (using if-feature)
I've attached just the change for the next revision of pkt-eca-policy that
includes the packet filter suggestions from I2NSF. This version of the
module is validated via pyang.
Sue
The L1 header involves the Sonet ring or OTN or DWDM as describe below:
// L1 header match identities
identity l1-header-match-type {
description
" L1 header type for match ";
}
identity l1-hdr-sonet-type {
base l1-header-match-type;
description
" L1 header sonet match ";
}
identity l1-hdr-OTN-type {
base l1-header-match-type;
description
" L1 header OTN match ";
}
identity l1-hdr-dwdm-type {
base l1-header-match-type;
description
" L1 header DWDM match ";
}
From: Linda Dunbar [mailto:linda.dunbar@huawei.com]
Sent: Thursday, June 30, 2016 5:15 PM
To: Susan Hares
Cc: i2rs@ietf.org
Subject: RE: [i2rs] relationship between
"draft-ietf-i2rs-pkt-eca-data-model-00.txt" and
"draft-ietf-i2rs-fb-rib-data-model-00"?
Sue,
Both those drafts are about YANG data models of Forwarding Rules based on
"L1/L2/L3/L4 header Matching Conditions". Why have two different YANG data
models?
p.s. pkt-eca-data-model even have L1 matching, which doesn't makes sense to
me. L1 is the transmission bit streams, terminated by the physical layer.
Linda
From: Susan Hares [mailto:shares@ndzh.com]
Sent: Thursday, June 30, 2016 9:12 AM
To: Linda Dunbar
Cc: i2rs@ietf.org
Subject: RE: [i2rs] relationship between
"draft-ietf-i2rs-pkt-eca-data-model-00.txt" and
"draft-ietf-i2rs-fb-rib-data-model-00"?
Linda:
The English text may be similar, but the yang data modules are different in
the drafts. Since filters are still under consideration, I wanted to handle
draft-ietf-i2rs-pkt-eca-data-model separately from the FB-RIB. The drafts
can be merged or left separate.
Is there a reason to merge these drafts?
Sue
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Wednesday, June 29, 2016 7:21 PM
To: Susan Hares
Cc: i2rs@ietf.org
Subject: [i2rs] relationship between
"draft-ietf-i2rs-pkt-eca-data-model-00.txt" and
"draft-ietf-i2rs-fb-rib-data-model-00"?
Sue, qin and Russ,
It seems to me that there are a lot of overlap between the following two
drafts:
- draft-ietf-i2rs-pkt-eca-data-model-00.txt
- draft-ietf-i2rs-fb-rib-data-model-00
they are all on forwarding packets based on matching criteria of various
packet headers (L2/L3/L4).
Why need two separate IDs?
Can we merge them?
Just curious.
Linda
- Re: [i2rs] relationship between "draft-ietf-i2rs-… Susan Hares
- Re: [i2rs] relationship between "draft-ietf-i2rs-… Linda Dunbar
- Re: [i2rs] relationship between "draft-ietf-i2rs-… Susan Hares
- [i2rs] relationship between "draft-ietf-i2rs-pkt-… Linda Dunbar