IETF Logo Mail Archive

Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00

Ted Lemon <mellon@fugue.com> Thu, 27 March 2014 12:34 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD371A066D for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 05:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 2TyQaasUSJXq for <homenet@ietfa.amsl.com>; Thu, 27 Mar 2014 05:34:29 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BBD831A066A for <homenet@ietf.org>; Thu, 27 Mar 2014 05:34:29 -0700 (PDT)
Received: from [172.16.0.56] (rrcs-67-78-65-202.sw.biz.rr.com [67.78.65.202]) by toccata.fugue.com (Postfix) with ESMTPSA id DAF512381509; Thu, 27 Mar 2014 08:34:24 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <5333D118.60404@globis.net>
Date: Thu, 27 Mar 2014 07:34:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C82BDDF-4E09-4536-9EF8-99EC4258E497@fugue.com>
References: <4943103B-77FB-4F95-A519-4FDE1246A128@nominet.org.uk> <53333F51.5030106@globis.net> <alpine.DEB.2.02.1403270703170.747@uplift.swm.pp.se> <5333D118.60404@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/BN6hkTIx6BnXG4dROWSqPo4eGps
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] WG adoption of draft-stenberg-homenet-hncp-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Mar 2014 12:34:30 -0000

On Mar 27, 2014, at 2:19 AM, Ray Hunter <v6ops@globis.net> wrote:
> So isn't the danger than HNCP starts off being very simple, and ends up duplicating a lot of previous work and experience?

If the working group submits HNCP for publication and it's morphed into a full-blown routing protocol, I will send it back (assuming I'm still AD at that point, and also in the unlikely event that I didn't intervene when someone proposed adding the ful-blown routing stuff).   I don't think anybody intends for this to happen, and if it does happen it will prevent the spec getting published, so I think we're pretty safe... :)

v2.23.0 | Report a Bug | By Email