Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

"Mark Baugher (mbaugher)" <mbaugher@cisco.com> Tue, 15 July 2014 21:32 UTC

Return-Path: <mbaugher@cisco.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 7AF301B295D for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 14:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 RNR8X87rcsb5 for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 14:32:30 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92D101B2950 for <homenet@ietf.org>; Tue, 15 Jul 2014 14:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2059; q=dns/txt; s=iport; t=1405459950; x=1406669550; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=0kwmYcPZd2AwlW9ustjOuFicueG9THZ3lqFmNQXICCc=; b=HSlKsMzcE1wJAH2/C5Nm/jOxkjBU7m+SXck861+EUvwxlwbaxSYFJUqP CbNSoP8V3Dq26DZFY2azj7UTg8ZNWVWsq4c28qcjElmDvXZU0s3cSvuqj Zw1kH+Plzzr3Yo2DiAfwFJK8PpVvO897LbsUeuokiLSxI6B9QhykpVPkD A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am0HAL2cxVOtJA2J/2dsb2JhbABZgw5SVwTBG1EKhnBTAYERFnWEAwEBAQMBAQEBawsFCwIBCBIGLicLFw4CBA4FiDoIDco7EwSPGDMHgy2BFgWbGJQlggKBQmyBRQ
X-IronPort-AV: E=Sophos;i="5.01,668,1400025600"; d="scan'208";a="61115285"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-5.cisco.com with ESMTP; 15 Jul 2014 21:32:29 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s6FLWT0O010348 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Jul 2014 21:32:29 GMT
Received: from xmb-aln-x10.cisco.com ([169.254.5.235]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Tue, 15 Jul 2014 16:32:29 -0500
From: "Mark Baugher (mbaugher)" <mbaugher@cisco.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Thread-Topic: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
Thread-Index: AQHPljWkESJkO5Is/kCoLOF/09bhG5uOeXaAgAAegACAAimYAIAAD/4AgAPFGv+AAr4jgIAAzOEAgAATGgCACOP0gIAAlRqAgAAEbACAABGaAIAAGpGAgAAC3QCAAC6tAA==
Date: Tue, 15 Jul 2014 21:32:29 +0000
Message-ID: <404C4648-278B-4369-9F44-692F9DD16FF2@cisco.com>
References: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com> <87fvij5wdw.wl.jch@pps.univ-paris-diderot.fr> <CADZyTkk2bv7T-Bs_ckG4i2MpXVDRqLA2R1dQgrMVrPSckOy-GQ@mail.gmail.com> <87k37uy703.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=YgD=JtyDpEz8TXOQmHxKzBoiEZbbW0LhZQy2GaKLqZQ@mail.gmail.com> <87vbrcydr9.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=kST4zPaPzz4DsAcCOtmYbQo-s2du+nEvJv0MSrneEMg@mail.gmail.com> <CADZyTkmZ+rC99qeC7gFEwc4JBoX9sHBUpo7p89+VC6zY7Z8drQ@mail.gmail.com> <87d2dfb98w.wl-jch@pps.univ-paris-diderot.fr> <CADZyTk=U25=Yck8BL5nrzGAR7mPk5HWp0r0h2wYy5ruSOf6rsQ@mail.gmail.com> <87vbr6mv8t.wl-jch@pps.univ-paris-diderot.fr> <7EEF5CD0-C3B8-4559-A75D-E55931F94F61@iki.fi> <21162.1405438875@sandelman.ca> <7ioawqpqcv.wl%jch@pps.univ-paris-diderot.fr> <7B5390DD-6969-4E26-A85E-0B436F48448F@fugue.com> <87a98acvxe.wl-jch@pps.univ-paris-diderot.fr> <E01C736F-75C0-436C-A283-28763208E46E@iki.fi>
In-Reply-To: <E01C736F-75C0-436C-A283-28763208E46E@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.83.69]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C76BD23D4F428C42B7E8668CD7923645@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Sw7Baza90i97oJb4gnwZbae2Rrs
Cc: "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Daniel Migault <mglt.ietf@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
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: Tue, 15 Jul 2014 21:32:32 -0000

On Jul 15, 2014, at 11:45 AM, Markus Stenberg <markus.stenberg@iki.fi>; wrote:

> On 15.7.2014, at 21.35, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>; wrote:
>>> I assume you mean that we need to recommend a default policy and also
>>> document the range of other policies that the end user might choose to
>>> use.
>> 
>> No, I just mean that Markus not wanting anything published in DNS is
>> policy, and that's completely independent of whether we want to define
>> a mechanism.  I have no opinion on either point.
>> 
>> All I know is that if we want to define a mechanism, then the mechanism
>> should be compatible with the worldview of HNCP, which includes things
>> such as multiple internal links and multiple CPEs.
> 
> The mechanism should not be tied to the particular ISPs either, except perhaps optionally.
> 
> In my case, I have 2 upstream ISPs, neither of which officially even admits IPv6 exists, but I _would_ like to publish my home v6 zone somewhere.. *sigh*
> 
> So to summarize:
> 
> - mechanism to publish either single DNS updates or zones would be nice to have (possibly with tie-in to service discovery)
> 
> - with policy bits thrown in 
> 
> and some sort of possible zero-conf use, with help of co-operating ISP perhaps, but _not_ requiring the first-hop ISP to be the only party you interact with.
> 
> The ‘homenet’ policy stuff may be actually relatively extensive in the end, although with some sort of reasonable zeroconf defaults.
> In this case, policy stuff should apply to what’s advertised (and in which scope), and where it can be reached from (firewalling either with accept rules, or PCP-derived holes).
> 
> (Hmm. We don’t seem to have any drafts on policy or management yet.)

There is some dependency on security for these.

Mark
> 
> Cheers,
> 
> -Markus
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet