Re: [teas-3272bis-design-team] 答复: 3272biss and YANG

Loa Andersson <loa@pi.nu> Thu, 07 March 2019 16:48 UTC

Return-Path: <loa@pi.nu>
X-Original-To: teas-3272bis-design-team@ietfa.amsl.com
Delivered-To: teas-3272bis-design-team@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F55113140D for <teas-3272bis-design-team@ietfa.amsl.com>; Thu, 7 Mar 2019 08:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eUmk0_qwCeGF for <teas-3272bis-design-team@ietfa.amsl.com>; Thu, 7 Mar 2019 08:48:51 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24561310A6 for <teas-3272bis-design-team@ietf.org>; Thu, 7 Mar 2019 08:48:50 -0800 (PST)
Received: from [10.255.250.60] (unknown [176.126.84.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 25A04180157E; Thu, 7 Mar 2019 17:48:43 +0100 (CET)
To: "Acee Lindem (acee)" <acee@cisco.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "julien.meuric@orange.com" <julien.meuric@orange.com>, "teas-3272bis-design-team@ietf.org" <teas-3272bis-design-team@ietf.org>
References: <1dc968ad-ed74-c058-a5f3-f098442c07ce@pi.nu> <018701d4d4c1$904da010$b0e8e030$@org.cn> <VI1PR07MB50406F2706E7681A23C84E61F04C0@VI1PR07MB5040.eurprd07.prod.outlook.com> <3611_1551957906_5C80FF92_3611_181_1_a4352131-ae50-4c5a-0a32-6748539424ae@orange.com> <VI1PR07MB50403113D750FC5DF0B1926EF04C0@VI1PR07MB5040.eurprd07.prod.outlook.com> <6100A065-79F2-4EFC-9257-3DF820322B51@cisco.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <077ff826-f9a6-0c2c-e676-0c732a9b7c93@pi.nu>
Date: Fri, 08 Mar 2019 00:48:40 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2
MIME-Version: 1.0
In-Reply-To: <6100A065-79F2-4EFC-9257-3DF820322B51@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-3272bis-design-team/zw2Bvd_quryXgXZ6xAH7pA44vDM>
Subject: Re: [teas-3272bis-design-team] 答复: 3272biss and YANG
X-BeenThere: teas-3272bis-design-team@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <teas-3272bis-design-team.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-3272bis-design-team/>
List-Post: <mailto:teas-3272bis-design-team@ietf.org>
List-Help: <mailto:teas-3272bis-design-team-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 16:48:54 -0000

Acee,

I did take quick look at the references of RFC3272, as you said the 
references are one of the benefits of the document.

However, looking at them today there is still some work to do, 
especially on the IETF documents, they have both been updated,
obsoleted and deprecated, some were not RFCs when 3272 were published,
but are referenced as "work in progress".

One other thing  is that they are not split in "Normative" and
"Informative" (don't know if we need to do the split), but does that
mean that we only have "Informative" references?

/Loa

On 2019-03-07 22:48, Acee Lindem (acee) wrote:
> One benefit of the original document was to provide references. I believe this is what the BIS should do as well. So, we'd provide a brief overview of YANG TE provisioning and then point to the reference models.
> 
> Thanks,
> Acee
> 
> On 3/7/19, 8:37 AM, "Teas-3272bis-design-team on behalf of Daniele Ceccarelli" <teas-3272bis-design-team-bounces@ietf.org on behalf of daniele.ceccarelli@ericsson.com> wrote:
> 
>      That's why i said "there is plenty" and not "everyone" 😊
>      
>      Jokes apart, even if it is 10% it's worth covering it IMO.
>      
>      Cheers
>      
>      Daniele
>      
>      -----Original Message-----
>      From: Teas-3272bis-design-team <teas-3272bis-design-team-bounces@ietf.org> On Behalf Of julien.meuric@orange.com
>      Sent: den 7 mars 2019 12:24
>      To: teas-3272bis-design-team@ietf.org
>      Subject: Re: [teas-3272bis-design-team] 答复: 3272biss and YANG
>      
>      Hi Daniele,
>      
>      > In hierarchical SDN all the traffic engineering is done with Restconf
>      + YANG.
>      
>      Not entirely true either. Ever read RFC 6805 or 7491? ;-b
>      
>      Julien
>      
>      
>      On 07/03/2019 11:33, Daniele Ceccarelli wrote:
>      > Well this is not entirely true.
>      > There is plenty of YANG Models for traffic engineering. TE-topology, TE-tunnel, TE-mapping...just to mention some of them.
>      > In hierarchical SDN all the traffic engineering is done with Restconf + YANG.
>      > I agree with Loa, it would be probably good to have at least a section dedicated to YANG.
>      > BR
>      >
>      > Daniele
>      >
>      > -----Original Message-----
>      > From: Teas-3272bis-design-team
>      > <teas-3272bis-design-team-bounces@ietf.org> On Behalf Of Aijun Wang
>      > Sent: den 7 mars 2019 09:42
>      >
>      > Yang is not closely related to the TE solution. Should we pay more attention to other emerged TE solutions for various environments?
>      >
>      >
>      > Best Regards.
>      >
>      > Aijun Wang
>      > Network R&D and Operation Support Department China Telecom Corporation Limited Beijing Research Institute,Beijing, China.
>      >
>      > -----邮件原件-----
>      > 发件人: Loa Andersson [mailto:loa@pi.nu]
>      > 发送时间: 2019年3月7日 15:45
>      >
>      >
>      > All,
>      >
>      > When 3272 was published, YANG modelling ws not over the horizon, is there anything we need to say in 3272bis about YANG?
>      >
>      > /Loa
>      >
>      
>      
>      _________________________________________________________________________________________________________________________
>      
>      Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>      
>      This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
>      If you have received this email in error, please notify the sender and delete this message and its attachments.
>      As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>      Thank you.
>      
>      --
>      Teas-3272bis-design-team mailing list
>      Teas-3272bis-design-team@ietf.org
>      https://www.ietf.org/mailman/listinfo/teas-3272bis-design-team
>      
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64