
From nobody Wed Nov 19 11:15:49 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56A551AD47E for <teas@ietfa.amsl.com>; Wed, 19 Nov 2014 11:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 FDrOKN3Qn6tC for <teas@ietfa.amsl.com>; Wed, 19 Nov 2014 11:15:43 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 356461AD486 for <teas@ietf.org>; Wed, 19 Nov 2014 11:15:40 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAJJFcAX023538 for <teas@ietf.org>; Wed, 19 Nov 2014 19:15:38 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAJJFbo5023528 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <teas@ietf.org>; Wed, 19 Nov 2014 19:15:37 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <teas@ietf.org>
Date: Wed, 19 Nov 2014 19:15:36 -0000
Message-ID: <036d01d0042d$3326bac0$99743040$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAELSl7b1VoPATHQKiAlLSHHnBD0A==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21116.002
X-TM-AS-Result: No--1.023-10.0-31-10
X-imss-scan-details: No--1.023-10.0-31-10
X-TMASE-MatchedRID: xsQGXiGsxCo1GNNcYTZ3yJ4CIKY/Hg3AtOt1ofVlaoJ1wPk/GHGZAwI/ +CyLz3dfklP9K0NxmNDdB/CxWTRRu4as+d5/8j56j2HvepvomBUJHZ8KXI8T4Q+HaUwqi/d922/ OyGpfKWlLIPMMdGsP3a9yxO5R6ODSiZDa+q6bAAVVQfzm8hzCuXYD/c2Xg/yR
Archived-At: http://mailarchive.ietf.org/arch/msg/teas/elXt2wEtd2PgS_lKhZ9pjwdZMHE
Subject: [Teas] Initial email to seed the archive
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 19:15:48 -0000

This is a first email to the TEAS mailing list to initiate the archive.


From nobody Wed Nov 19 12:30:31 2014
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2D71A6F22; Wed, 19 Nov 2014 12:22:15 -0800 (PST)
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] autolearn=ham
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 7DBxbnyg4brL; Wed, 19 Nov 2014 12:22:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACB71A1B82; Wed, 19 Nov 2014 12:22:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141119202211.5915.48053.idtracker@ietfa.amsl.com>
Date: Wed, 19 Nov 2014 12:22:11 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/teas/d7es3QwqVPV5eIiTqbyZpc5x6TM
X-Mailman-Approved-At: Wed, 19 Nov 2014 12:30:30 -0800
Cc: lberger@labn.net, teas@ietf.org, db3546@att.com
Subject: [Teas] New Non-WG Mailing List: Teas -- Traffic Engineering Architecture and Signaling working group discussion list
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 20:22:16 -0000

A new IETF non-working group email list has been created.

List address: teas@ietf.org
Archive: http://www.ietf.org/mail-archive/web/teas/current/maillist.html
To subscribe: https://www.ietf.org/mailman/listinfo/teas

Purpose:

This list is for the discussion of architectures for Traffic Engineered networks and for signaling techniques utilising RSVP-TE. 


For additional information, please contact the list administrators.


From nobody Fri Nov 28 01:24:50 2014
Return-Path: <db3546@att.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFEB1A1ADD; Fri, 28 Nov 2014 01:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WGOEmm_LoOVo; Fri, 28 Nov 2014 01:24:43 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1975E1A1AF9; Fri, 28 Nov 2014 01:24:43 -0800 (PST)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.2-0) over TLS secured channel with ESMTP id a5f38745.0.7032278.00-2384.19799484.nbfkord-smmo07.seg.att.com (envelope-from <db3546@att.com>);  Fri, 28 Nov 2014 09:24:43 +0000 (UTC)
X-MXL-Hash: 54783f5b38fd24a0-6db3dad5f7340b6c192ac6a1883a941d5f6f895b
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id sAS9OfhV000595; Fri, 28 Nov 2014 04:24:42 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id sAS9Oa9Y000567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Nov 2014 04:24:38 -0500
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Fri, 28 Nov 2014 09:24:28 GMT
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.4]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0195.001; Fri, 28 Nov 2014 04:24:28 -0500
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: "ccamp@ietf.org" <ccamp@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: TE Topology YANG Model Work
Thread-Index: AdAK7Q+YSS5NPSwJRtiP5yEvNWYy6g==
Date: Fri, 28 Nov 2014 09:24:27 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C816715D3B@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.47.123]
Content-Type: multipart/alternative; boundary="_000_F64C10EAA68C8044B33656FA214632C816715D3BMISOUT7MSGUSRDE_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=Fq2yCRXq c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=oQASVyGzVcYA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=XIqp]
X-AnalysisOut: [o32RAAAA:8 a=5y4faFyK3SkA:10 a=UkWLIDYav5TIAikMWuMA:9 a=Cj]
X-AnalysisOut: [uIK1q_8ugA:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=5Bdoco]
X-AnalysisOut: [O31hphY62w:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <db3546@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: http://mailarchive.ietf.org/arch/msg/teas/uHgrG5OuPyIKbGtlgjlMbhJTYaM
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, Lou Berger <lberger@labn.net>, "BRUNGARD, DEBORAH A" <db3546@att.com>
Subject: [Teas] TE Topology YANG Model Work
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Nov 2014 09:24:44 -0000

--_000_F64C10EAA68C8044B33656FA214632C816715D3BMISOUT7MSGUSRDE_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We wanted to let folks know about some pending activity on the TE yang mode=
ls. The core of this work seems headed to the TEAS WG. In the interim, we a=
re looking at establishing a short lived TE topology YANG model Design Team=
. The goal of the DT will be to produce a consolidated draft in time for di=
scussion in Dallas, with an expectation that the document will become a TEA=
S WG draft post Dallas.

The DT is expected to be composed of folks who are already contributing/act=
ive in this area. (additional volunteers can let us know, off-list.)

We also expect to announce an interim on this topic in the next few days. W=
e're targeting this meeting for ~3 weeks+-.

Deborah and Lou



--_000_F64C10EAA68C8044B33656FA214632C816715D3BMISOUT7MSGUSRDE_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi,</div>
<div>&nbsp;</div>
<div>We wanted to let folks know about some pending activity on the TE yang=
 models. The core of this work seems headed to the TEAS WG. In the interim,=
 we are looking at establishing a short lived TE topology YANG model Design=
 Team. The goal of the DT will be
to produce a consolidated draft in time for discussion in Dallas, with an e=
xpectation that the document will become a TEAS WG draft post Dallas.</div>
<div>&nbsp;</div>
<div>The DT is expected to be composed of folks who are already contributin=
g/active in this area. (additional volunteers can let us know, off-list.)</=
div>
<div>&nbsp;</div>
<div>We also expect to announce an interim on this topic in the next few da=
ys. We're targeting this meeting for ~3 weeks&#43;-.</div>
<div>&nbsp;</div>
<div>Deborah and Lou</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_F64C10EAA68C8044B33656FA214632C816715D3BMISOUT7MSGUSRDE_--


From nobody Fri Nov 28 08:32:30 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1CA1A7012; Tue, 25 Nov 2014 13:12:53 -0800 (PST)
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] autolearn=ham
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 8QnMa5j7gmyc; Tue, 25 Nov 2014 13:12:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 229EE1A6FE6; Tue, 25 Nov 2014 13:12:51 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141125211251.4012.31238.idtracker@ietfa.amsl.com>
Date: Tue, 25 Nov 2014 13:12:51 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/teas/l39pbccCAdbFrbgrUdANE8JN5EE
X-Mailman-Approved-At: Fri, 28 Nov 2014 08:32:29 -0800
Cc: teas WG <teas@ietf.org>
Subject: [Teas] WG Review: Traffic Engineering Architecture and Signaling (teas)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Nov 2014 21:12:54 -0000

A new IETF working group has been proposed in the Routing Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2014-12-02.

Traffic Engineering Architecture and Signaling (teas)
------------------------------------------------
Current Status: Proposed WG

Chairs:
  Deborah Brungard <db3546@att.com>
  Lou Berger <lberger@labn.net>

Assigned Area Director:
  Adrian Farrel <adrian@olddog.co.uk>

Mailing list
  Address: teas@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/teas
  Archive: http://www.ietf.org/mail-archive/web/teas/

Charter:

The Traffic Engineering Architecture and Signaling (TEAS) Working
Group is responsible for defining MPLS and GMPLS traffic 
engineering architecture, standardizing the RSVP-TE signaling
protocol, and identifying required related control-protocol 
functions, i.e., routing and path computation element functions. 

Traffic Engineering (TE) is the term used to refer to techniques
that enable operators to control how specific traffic flows are 
treated within their networks. TE is applied to packet networks 
via MPLS TE tunnels and LSPs. The MPLS-TE control plane was
generalized to additionally support non-packet technologies via
GMPLS.  RSVP-TE is the signaling protocol used for both MPLS-TE
and GMPLS.

The TEAS WG is responsible for:

 a) Traffic-engineering architectures for generic applicability
    across packet and non-packet networks. This includes both 
    networks that include the use of PCE and those that do not.
    The PCE architecture itself is out of the WG scope.

 b) Definition of protocol-independent metrics and parameters 
    (measurement and/or service attributes) for describing 
    links and tunnels/paths required for traffic engineering
    (and related routing, signaling and path computation). 
    These will be developed in conjunction with requests and
    requirements from other WGs to ensure overall usefulness.

 c) Functional specification of extensions for routing (OSPF,
    ISIS) and for path computation (PCE) to provide general 
    enablers of traffic-engineering systems that also use 
    RSVP-TE. Protocol formats and procedures that embody these
    extensions will be done in coordination with the WGs 
    supervising those protocols.

 d) Functional specification of generic (i.e., not data plane
    technology-specific) extensions for RSVP-TE, and the 
    associated protocol formats and procedures that embody 
    these extensions. 

 e) Definition of control plane mechanisms and extensions to allow
    the setup and maintenance of TE paths and TE tunnels that span 
    multiple domains and/or switching technologies, where a 
    domain may be an IGP area, an Autonomous System, or any other
    region of topological visibility. 

 f) Definition and extension of management and security techniques 
    for RSVP-TE signaling. This includes configuring and monitoring
    RSVP-TE as well as mechanisms used to configure, control, and 
    report OAM within TE networks. YANG and MIB modules may be
    considered.

The TEAS working group is chartered to deliver the following:

 1. Definition of additional abstract service, link, and path 
    properties such as jitter, delay, and diversity. Extensions 
    to IGPs to advertise these properties, and extensions to 
    RSVP-TE to request and to accumulate these properties. Work
    with PCE WG to include these properties in computation 
    requests.

 2. Specification of terminology, architecture, and protocol
    requirements for abstraction and distribution of TE 
    information between interconnected TE domains/layers.

 3. Specification and protocol extensions for a GMPLS External
    Network-to-Network Interface (E-NNI), i.e., multi-domain 
    GMPLS support.

 4. Protocol mechanisms to signal associated LSPs in particular
    with different source nodes.

 5. Requirements and protocol extensions for additional protection
    mechanisms including end-point protection, protection of P2MP 
    LSPs, and inter-domain protection.

 6. YANG models for a Traffic Engineering Database in coordination
    with working groups working on YANG models for network
    topology and for technology-specific network attributes.

Requirements may be documented in stand-alone RFCs, may be
folded into architecture or solutions RFCs, may be recorded on a
wiki, or may be documented in an Internet-Draft that is not 
progressed to RFC.

The TEAS WG will coordinate with the following working groups:

 - With the MPLS WG to maintain and extend MPLS-TE protocol
   mechanisms and to determine whether they should be generalized.
 
 - With the CCAMP WG to maintain and extend non-packet, data plane
   technology-specific TE protocol mechanisms and to determine 
   whether they should be generalized.

 - With the OSPF and ISIS WGs to maintain or extend TE routing 
   mechanisms for MPLS-TE and GMPLS.

 - With the PCE WG on uses of a PCE in the traffic-engineering 
   architecture, on PCE extensions per the above, and on RSVP-TE
   extensions to support PCE WG identified requirements.

 - With the IDR WG on the use of BGP-LS in TE environments.

In doing this work, the WG will cooperate with external SDOs (such
as the ITU-T and the IEEE 802.1) as necessary.

Milestones:

TBD

