[CCAMP] Fwd: RFC 8776 on Common YANG Data Types for Traffic Engineering

t petch <ietfa@btconnect.com> Fri, 12 June 2020 11:18 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0263A3A0F49 for <ccamp@ietfa.amsl.com>; Fri, 12 Jun 2020 04:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.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 2lU5iBpti-GM for <ccamp@ietfa.amsl.com>; Fri, 12 Jun 2020 04:18:17 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00100.outbound.protection.outlook.com [40.107.0.100]) (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 3D7A33A0F48 for <ccamp@ietf.org>; Fri, 12 Jun 2020 04:18:16 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aQQN64OSD1LSNbnb+a3+/gJTjRBo6HTwxv5ZCDqqS97KtulQ82Z0Fam8S5p1P7y1t5xjSkxNy9oHU7xyJYyPS5FUeIbnq+0W9rM5VjY8Kpt9vEGmtOODKcCpP55At6oNyVTmAQsgcvEe5GuNKJ2gChryWW93Oy/XaPLUwiQOMVpqG+rhwsIBsmPS/hTRnlFDO6ZcYUAl5hc5CjwVr63ToZOXMAtfMU8i2GUG4c56ofqmNkdUwMuUTf42rOwQnOf/LI9LNbv55RmN385NlovSNroKl8MwfYkKtG7dbniHJuFaZNrAqBMoP8bTA1vdJS9AmgsKPXbekEIw1Z1PueQodg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jTZlkUgklMMTRfuXWMB99yI1FecteA1mKakwAuEcfVk=; b=RBYUFLwk1wwvwcyE9UyUeS5pDanCebZYrVCWqemxi/A7gMQjpFueNng1auMIj+dLPEyYRRFcGHHkiy1iiprY74KWWX/6IQwnBPKQMNlHfeLfG46rkPpqC9WF/KIjKgyjJk7OQxVLkFbtg2qqDIS9GhvKQgF8NwyXVpBjsfhodj55Y1L3xOOYj7QnlxKdiSwC2sf8liWqdPWPNpNjqmFuok4tjR4rzjVbqSoIxUHjo3MXCTGjR/uFKF2MpJARA4CL7loh7cJfnbZgpE80UiptG54pT69JnONWsK4F2R3l8AZwlipOYAw++72EPsKmpISd5QL6L/XfoOQY0UW9Qns5uA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jTZlkUgklMMTRfuXWMB99yI1FecteA1mKakwAuEcfVk=; b=x6ep0jgCUSAAZB560SZYztkhWH6Hg3lsrO00nPhjk1CKYShv5MvoBxH4/s9k95f5CSmSeTa7tl9VdRp+kKarG5RYnzgH+e3hh4ub4gfm12TuoPx51XWV+cKxPf9wTGlBK8yXmiiGwssrYg+aHuaS1pVlXl17HqpuZJrd+dJsdko=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25) by DB7PR07MB5497.eurprd07.prod.outlook.com (2603:10a6:10:7a::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.9; Fri, 12 Jun 2020 11:18:14 +0000
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::6d73:b879:b380:bed4]) by DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::6d73:b879:b380:bed4%7]) with mapi id 15.20.3088.019; Fri, 12 Jun 2020 11:18:14 +0000
To: ccamp@ietf.org
From: t petch <ietfa@btconnect.com>
X-Forwarded-Message-Id:
Message-ID: <5EE3646D.7080506@btconnect.com>
Date: Fri, 12 Jun 2020 12:18:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LNXP265CA0075.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:76::15) To DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.139.211.47) by LNXP265CA0075.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:76::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3088.20 via Frontend Transport; Fri, 12 Jun 2020 11:18:13 +0000
X-Forwarded-Message-Id:
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 02f23d5d-62e3-4451-bf2f-08d80ec24c31
X-MS-TrafficTypeDiagnostic: DB7PR07MB5497:
X-Microsoft-Antispam-PRVS: <DB7PR07MB549708D5E9992D2BA0234B83A2810@DB7PR07MB5497.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:6790;
X-Forefront-PRVS: 0432A04947
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: A/PU16GqnCb1//tIGtLB8RoJ6WX+3taKh5makVGceV8frEjV7Ad43LCekUhIdUJE/qNwwfuZX3j8hMMCkjRjYmLB3OoGVGat4f+ik/78rQcIkthtidmbgrXPVrQhWNf4o97pbNcis7wDtvYjcjHU9/hy8GcIT62p3KPMkh4rFC/qbUifNsq9gJbh6lb0cUawV5tzmb4BCddoXtUq6Ze5IqVKoMjxZ1FlXJA8rXP2D3nYYfvmeZwNGClQd/qMIeIEh9ip34HvlY05fzflhMcHje5OkePNPAlELbcglAI3/tNq1n9jzBjKNkHbw8YIbts6NwwRr3TwJWQz92Y74Fls0B3MQVwnWMLT9u6mnstylXWEGhdUiLW4w6Fgh0wQqlKD5rrZqjr3cTKcEpLIZbT3cQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5340.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(366004)(396003)(346002)(376002)(39860400002)(136003)(316002)(66476007)(2906002)(6916009)(8676002)(66556008)(66946007)(33656002)(8936002)(6486002)(87266011)(2616005)(956004)(16576012)(66574014)(86362001)(36756003)(478600001)(5660300002)(186003)(52116002)(83380400001)(6666004)(16526019)(26005)(966005); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: lM1U0VBs2OG224GfblY9y2NEoEa+JzxA9MkCVWEUVvBj6ETh3ACyYzrolKfutRrZOn16WsDpoK3S1I7UGKzWNZiKDFOm/dY58WyTohw8or++TNCZb/rPThcaz9AXUe7UBypEpWUFNzUAwLh4StFuT/eGBEbSkdUFYtRrOfJzEdhOMwVScz6WrwMFZyCQ1QZpXiopY4nMjW+A7pCn5Ep5nc43ygYWKJwX81GWidQaEeyNHqtTtewUaZ818XOTaiD1zTiEiSyDnh6YrNcydqs0qHVsaKH6G8tVoTUBM27sv9yXm5f/a9Msqd9Sz4zZi/L5og68ma8jj9QkYVtjpqzagGs7AL534LnZ7ZG7LHQyYJeJEJaMPf97kG9J1aLOw7oqyoSfSpgoWl5RKpkUXuxEhwmh1ROvv9b1p+xN7pLLkWr1fLrFLmGay5uiaM1QA1UCHBiPuwjZq3NsywQubAURTzNQnQjLACpG7J8qHrjLJi0=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 02f23d5d-62e3-4451-bf2f-08d80ec24c31
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Jun 2020 11:18:14.4365 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: AV0zboZ/F2LBeBrse3HI05MsZYmRRxCuZUt2l2dJ3kb55/VFYLJtyev05YGFnV7jLNG9/JB5tOA4mWdMJNA0Vg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5497
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/0FGAuEi5fjItN-pfsOJUp6n7Qg0>
Subject: [CCAMP] Fwd: RFC 8776 on Common YANG Data Types for Traffic Engineering
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2020 11:18:20 -0000

Now all those references will need updating:-)

Tom Petch

-------- Forwarded Message --------
Subject: RFC 8776 on Common YANG Data Types for Traffic Engineering
Date: 11 Jun 2020 01:29
From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org

A new Request for Comments is now available in online RFC libraries.


         RFC 8776

         Title:      Common YANG Data Types for
                     Traffic Engineering
         Author:     T. Saad,
                     R. Gandhi,
                     X. Liu,
                     V. Beeram,
                     I. Bryskin
         Status:     Standards Track
         Stream:     IETF
         Date:       June 2020
         Mailbox:    tsaad@juniper.net,
                     rgandhi@cisco.com,
                     xufeng.liu.ietf@gmail.com,
                     vbeeram@juniper.net,
                     i_bryskin@yahoo.com
         Pages:      84
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-teas-yang-te-types-13.txt

         URL:        https://www.rfc-editor.org/info/rfc8776

         DOI:        10.17487/RFC8776

This document defines a collection of common data types and groupings
in YANG data modeling language. These derived common types and
groupings are intended to be imported by modules that model Traffic
Engineering (TE) configuration and state capabilities.

This document is a product of the Traffic Engineering Architecture and 
Signaling Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   https://www.ietf.org/mailman/listinfo/ietf-announce
   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
.