[OSPF] Application Specific TE-link attributes -- Modeling reference from TEAS WG
Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com> Fri, 31 March 2017 17:32 UTC
Return-Path: <vishnupavan.ietf@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13EE412952D for <ospf@ietfa.amsl.com>; Fri, 31 Mar 2017 10:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Jfuw6DvjDHYO for <ospf@ietfa.amsl.com>; Fri, 31 Mar 2017 10:31:59 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 72B781294BF for <ospf@ietf.org>; Fri, 31 Mar 2017 10:31:59 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id 190so15854010itm.0 for <ospf@ietf.org>; Fri, 31 Mar 2017 10:31:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=XM461CM1i0oat06xpmmSiYIxfRT6FLFaE+q/GSO000U=; b=L9O9v11qWjYe+zw1JVvQKgPxoowUbYG+70f+NX9OY5MGTnDRehVwH4pg8cJbeLtljO d0nUoidq3ozqvsb0QK0z6cO13aVi9Q9jRi04WYuImXZtUJ9FdnfElJ+33YV3M/Tigzkb cZxo/3kdMMtaOYRtBzyJ0EixojOQVyKeAp3jNuQIqbzI2dozp7DzDEEX0x08EtatJupO Shygy9DG4WGILY39JDbS7wdz5qUEkJIK8As5gfHCRNiPrSH4SOdRRYo+3xbxkM0IwI+f X0xYFE+2NHyCKq6TdxYJma0YN9Ntd7EWrrgfw0HI4CaYKSGtvIrTc7tkrCk3aw5L7ygF k9Sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=XM461CM1i0oat06xpmmSiYIxfRT6FLFaE+q/GSO000U=; b=CcLQWUvznaDeRHE+p9EvZYfQ6b3oQmETdFe3+WQT//A7OK8x17XsgEuAV35yu6Awr3 WM7QeQ7MavUZkaMRcppZqF5ILIHjNvNBlDz3A/i0UAcnps7XGJ+a+uz8+Fq0UtaRkNtV YWDToHw4UhbIBA2HdNumQ7WgbkTITZHTxxs5YzSTkLoCLEUaCxfnL1m34yApPFv7hvqM FaZ4uatqzpktvSOiiI10+JMnEOtR8+Uz3u1rj2RIZXiQm6JHscaaF4B+E8GKvBY5agDu i94dV3BVS5/lHNRW6FKO6qN+hiVJlaRZyee71xO0aHqlnRjH42lCpHJt4f3SVY6SqnRr M0FQ==
X-Gm-Message-State: AFeK/H2KorZ1OqulCjS27D1Z7Gs9QUWN30JWeMCYKQv/662FT+7Jp5Fvm1t9o1JTgspKyZoukUzMetonWrA75A==
X-Received: by 10.36.115.145 with SMTP id y139mr4625502itb.123.1490981518742; Fri, 31 Mar 2017 10:31:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.185.137 with HTTP; Fri, 31 Mar 2017 10:31:58 -0700 (PDT)
From: Vishnu Pavan Beeram <vishnupavan.ietf@gmail.com>
Date: Fri, 31 Mar 2017 13:31:58 -0400
Message-ID: <CAMoPOh=PrBam0GzeuFEDFULyUBxQ6bTGoVfP8A+rbRXgSh43_g@mail.gmail.com>
To: ospf@ietf.org
Content-Type: multipart/alternative; boundary="001a114526cccaa34b054c0a2f02"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/iFnLGSjlnVQF7m2g4Ty8lOn82H0>
Subject: [OSPF] Application Specific TE-link attributes -- Modeling reference from TEAS WG
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2017 17:32:01 -0000
Folks, Hi! As mentioned in the WG session yesterday, the authors of the TE-Topology model discussed modeling per-TE-application attributes sometime late last year. The email from the link below (courtesy - TEAS WG ML archives) talks about what the design team ended up proposing: https://mailarchive.ietf.org/arch/msg/teas/6wnqXEkxSyGZxmDQqH6FaTYkDJ4 In the model, we have a set of te-attributes that sits inside the te-link container – these are the per-te-link attributes that are up for grabs by any te-application (as deemed fit). We also have a list of te-applications under each te-link entry, indexed by an application-type (identityref) – the type could be RSVP-TE or SR-TE or any custom te-application. The attributes specific to a given te-application are specified explicitly under the te-application list-entry. Regards, -Pavan
- [OSPF] Application Specific TE-link attributes --… Vishnu Pavan Beeram