Re: [i2rs] 'network type' placement and RFC8345
Lou Berger <lberger@labn.net> Sat, 26 September 2020 14:00 UTC
Return-Path: <lberger@labn.net>
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 11F503A0990 for <i2rs@ietfa.amsl.com>; Sat, 26 Sep 2020 07:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 PdqqrNfoy-7S for <i2rs@ietfa.amsl.com>; Sat, 26 Sep 2020 07:00:09 -0700 (PDT)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C78043A098D for <i2rs@ietf.org>; Sat, 26 Sep 2020 07:00:09 -0700 (PDT)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 754099E8603FB for <i2rs@ietf.org>; Sat, 26 Sep 2020 08:00:00 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id MAk4k8O9SWYdhMAk4kmJrz; Sat, 26 Sep 2020 08:00:00 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=CYomGojl c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=xqWC_Br6kY4A:10:nop_ipv6 a=IkcTkHD0fZMA:10:nop_charset_1 a=reM5J-MqmosA:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=48vgC7mUAAAA:8 a=TWcEkWJUgOrtNDOlHqMA:9 a=lm-OBoNNGzlfUVCy:21 a=JbHyfGmid4RtRfi8:21 a=QEXdDO2ut3YA:10:nop_charset_2 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=FFNmE/MlVUHhgwmEbVG634qAGFfPsR9MAaZNK2A0UD4=; b=09YWiswHTmzKEE56muCLaOj8EH Xinn5o0/FkMEPNT7csSCnrrRNQ/2ALshX5b3kPZHknM1OH1QyUPPBpWmymdaepjPCx4i93RID17MJ jcqzNV7dcYVWdYqKlQiwG0gl2;
Received: from [127.0.0.1] (port=57009 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <lberger@labn.net>) id 1kMAk4-001pvN-7l; Sat, 26 Sep 2020 08:00:00 -0600
To: tom petch <ietfc@btconnect.com>, Susan Hares <shares@ndzh.com>, 'Qin Wu' <bill.wu@huawei.com>
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABAADA0A35D@dggeml511-mbs.china.huawei.com> <AM7PR07MB624872A7B76D2FAE9D347A2FA0360@AM7PR07MB6248.eurprd07.prod.outlook.com> <007201d6933d$3726b4e0$a5741ea0$@ndzh.com> <AM7PR07MB62482DE49013C999B50C2707A0360@AM7PR07MB6248.eurprd07.prod.outlook.com> <02c001d69388$cd8a0c20$689e2460$@ndzh.com> <VI1PR07MB62563F2A24E3885163819D90A0370@VI1PR07MB6256.eurprd07.prod.outlook.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9e5f593f-d160-f9bb-ede1-d2642f5d6374@labn.net>
Date: Sat, 26 Sep 2020 09:59:59 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <VI1PR07MB62563F2A24E3885163819D90A0370@VI1PR07MB6256.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Source-L: Yes
X-Exim-ID: 1kMAk4-001pvN-7l
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([IPv6:::1]) [127.0.0.1]:57009
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/ove5_x1ts4AJ6-o0hHb8Fhb4mi0>
Subject: Re: [i2rs] 'network type' placement and RFC8345
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 26 Sep 2020 14:00:11 -0000
Tom, On 9/26/2020 7:06 AM, tom petch wrote: > I have read and re-read RFC8345 and as I have said, I find it clear that a > presence container must be defined but do not see the guidance as to what > goes under what, apart from OSPF and layer 3. As other messages makes clear, there's a lot of history here. The assumption has always been that technologies controlled using TE mechanisms/models of the IETF (including those worked on in CCAMP) would be based on the generic TE models developed in TEAS. I think the documents developed in CCAMP make this hierarchy clear -- but perhaps I've been too close to those discussions. FWIW https://tools.ietf.org/html/rfc8795#section-6 is pretty clear on this. I suggest moving this discussion back to CCAMP or TEAS for follow up focused on the ccamp document or teas-produced RFC... Lou
- [i2rs] 'network type' placement and RFC8345 tom petch
- Re: [i2rs] 'network type' placement and RFC8345 Qin Wu
- Re: [i2rs] 'network type' placement and RFC8345 tom petch
- Re: [i2rs] 'network type' placement and RFC8345 Qin Wu
- Re: [i2rs] 'network type' placement and RFC8345 tom petch
- Re: [i2rs] 'network type' placement and RFC8345 BRUNGARD, DEBORAH A
- Re: [i2rs] 'network type' placement and RFC8345 Susan Hares
- Re: [i2rs] 'network type' placement and RFC8345 tom petch
- Re: [i2rs] 'network type' placement and RFC8345 Susan Hares
- Re: [i2rs] 'network type' placement and RFC8345 tom petch
- Re: [i2rs] 'network type' placement and RFC8345 Lou Berger