[mpls] Thoughts on draft-saad-mpls-lsp-instant-install-rsvpte

"Adrian Farrel" <adrian@olddog.co.uk> Sun, 08 November 2015 10:03 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288D41A19E3 for <mpls@ietfa.amsl.com>; Sun, 8 Nov 2015 02:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.9
X-Spam-Level:
X-Spam-Status: No, score=-99.9 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 CU_Jec8x7cQD for <mpls@ietfa.amsl.com>; Sun, 8 Nov 2015 02:03:27 -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 5F7FA1A06FD for <mpls@ietf.org>; Sun, 8 Nov 2015 02:03:27 -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 tA8A3PAG018199 for <mpls@ietf.org>; Sun, 8 Nov 2015 10:03:25 GMT
Received: from 950129200 (jplon-nat12.juniper.net [193.110.55.12]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id tA8A3HCT018124 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <mpls@ietf.org>; Sun, 8 Nov 2015 10:03:22 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org
Date: Sun, 08 Nov 2015 10:03:12 -0000
Message-ID: <007e01d11a0c$b2b9b620$182d2260$@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: AdEaDD8zekJSNAdgSTOCzuved2LdFw==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-21928.006
X-TM-AS-Result: No--6.066-10.0-31-10
X-imss-scan-details: No--6.066-10.0-31-10
X-TMASE-MatchedRID: ZEpaGrJ+tTPaSvM1wIoVPkM/y5EMs/JmgHzgwy8qV5oX7v80pLvlB2d8 HN3h9yU8RfZg1W0RnrHZi84ijSgzfGedc+HgwP0hMN+B8zdlz9GRPtwwl97om0wND0YI1OK1kwE 2YUcQMETi8zVgXoAltlwtzewu2M63tuZmiwj/lnLdB/CxWTRRu4as+d5/8j56+vxuKpmt72vXG/ ZIKiCQLLDfY8L9CyR+sGKbXTsqTDt2madUWCN/8Q==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/7asQC-3QoGx7PfCuVKhnYa7dTiE>
Subject: [mpls] Thoughts on draft-saad-mpls-lsp-instant-install-rsvpte
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Nov 2015 10:03:29 -0000

Hi authors,

You say:

   In practice, however, the RSVP
   Resv message for the new LSP can reach the ingress before one (or
   more) LSR(s) have completed programming their forwarding for the new
   LSP. 

I suppose we are falling into the variation cases of 3209's "SHOULD".

      The node SHOULD be prepared to
      forward packets carrying the assigned label prior to sending the
      Resv message.

Indeed, pipelining seems to be quite as common in packet networks as it is in
optical networks.

You might find RFC 6383 useful reading.

Adrian