IETF Logo Mail Archive

[nvo3] Applicability of RFC 5512 to NVO3?

Shane Amante <shane@castlepoint.net> Sat, 18 February 2012 06:28 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D8621E8023 for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 22:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HGJRpX5VDYpY for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 22:27:59 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id A5B8521F86C7 for <nvo3@ietf.org>; Fri, 17 Feb 2012 22:27:59 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id 1BB18268063; Fri, 17 Feb 2012 23:27:57 -0700 (MST)
Received: from mbpw.castlepoint.net (63-225-243-189.hlrn.qwest.net [63.225.243.189]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for nvo3@ietf.org; Fri, 17 Feb 2012 23:27:57 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=63.225.243.189; client-port=57628; syn-fingerprint=65535:54:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
From: Shane Amante <shane@castlepoint.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Feb 2012 23:27:40 -0700
Message-Id: <07A3C8B8-1460-435C-99B6-210B479C3840@castlepoint.net>
To: nvo3@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [nvo3] Applicability of RFC 5512 to NVO3?
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "L2 \"Network Virtualization Over l3\" overlay discussion list \(nvo3\)" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2012 06:28:00 -0000

I am curious to know if the following RFC has been looked at to see if it's applicable to the NVO3 solution space. Furthermore, if it was looked at, I'd be curious to know why it was insufficient?

http://tools.ietf.org/html/rfc5512

Thanks,

-shane

v2.23.0 | Report a Bug | By Email