IETF Logo Mail Archive

Re: [homenet] Multicast scoping

Mark Townsley <mark@townsley.net> Thu, 07 November 2013 18:14 UTC

Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72CD11E81C4 for <homenet@ietfa.amsl.com>; Thu, 7 Nov 2013 10:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.153
X-Spam-Level:
X-Spam-Status: No, score=-3.153 tagged_above=-999 required=5 tests=[AWL=0.445, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 whxPKPqkZyVO for <homenet@ietfa.amsl.com>; Thu, 7 Nov 2013 10:14:50 -0800 (PST)
Received: from mail-bk0-f47.google.com (mail-bk0-f47.google.com [209.85.214.47]) by ietfa.amsl.com (Postfix) with ESMTP id 182EF11E822F for <homenet@ietf.org>; Thu, 7 Nov 2013 10:12:43 -0800 (PST)
Received: by mail-bk0-f47.google.com with SMTP id d7so372516bkh.6 for <homenet@ietf.org>; Thu, 07 Nov 2013 10:12:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=j65FS/G2Us9RRJo9kTLstTGyWcNUC6hYlFj8e1uWka8=; b=Z3WYLHq7jPs+4+HEBYPiBgXFVgUs/0wR8T7C3XNV9y2yw4DjC6VOokr3Aiad+v3pxK jkSkcb5mxWNa4llFSLN28fhq9FRN9wdZZkKNSorklj7DkQtpMk8ysCSZIH4ONsRR2rum tCtWbbq4fUxa63HOoSwMEhjuTjQgNcTHvwfs/ta2jNgSJ1+lxxDuqQUmuNAdPOVPfhfN omFf61O9b2+LbylwegD7BXtc0n+v16vHFN3+dHHypA2HJ/M0oX0FXHjxt1U8GTNVBzXa v5wyHkwTrUkqIestS5FNGyzvPP0OeQBRXkkS6KVFGOgo/rZAepQYOYQGh0rNSgTrifZE sUjw==
X-Gm-Message-State: ALoCoQkE8k2jVlhD0crnAXMNaoiTiUk4wWzE50cGJkBdQBpMdbC/kYxold8QjXMPuy02nFuXjmkl
X-Received: by 10.204.68.3 with SMTP id t3mr7422152bki.33.1383847949291; Thu, 07 Nov 2013 10:12:29 -0800 (PST)
Received: from dhcp-a4b2.meeting.ietf.org (dhcp-a4b2.meeting.ietf.org. [31.133.164.178]) by mx.google.com with ESMTPSA id qe6sm3171981bkb.5.2013.11.07.10.12.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Nov 2013 10:12:28 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_936B8953-B9CE-4D95-B8A0-EB225837AC5F"
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <527BD67D.8070906@innovationslab.net>
Date: Thu, 07 Nov 2013 10:12:25 -0800
Message-Id: <B13975B2-06A8-402B-8C1C-4AEA830155E0@townsley.net>
References: <527BD67D.8070906@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1283)
Cc: homenet@ietf.org
Subject: Re: [homenet] Multicast scoping
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Nov 2013 18:14:55 -0000

This part of the agenda today includes quite a bit on the thorny problem of Border Discovery, you are more the welcome to join if you can!

Security
  1040 Michael Behringer, draft-behringer-homenet-trust-bootstrap-01 (10 min)
  1050 Markus Stenberg and Erik Kline, draft-kline-homenet-default-perimeter-00
  (implementation report) (15 min)
Homenet / HIPnet Design Team Results
  1105  Timothy Winters, draft-winters-homenet-sper-interaction-00 (20 min)

On Nov 7, 2013, at 10:05 AM, Brian Haberman wrote:

> All,
>     I seem to be the bane of homenet given my stance on multicast scope
> zones.  Probably because I am a co-author on RFC 4007. :)
> 
>     After some discussions, it seems there is a reasonable way to allow
> the homenet arch to use the admin-scope multicast range.  My original
> concern, as documented in my DISCUSS, is that RFC 4291 requires scope 4
> and larger be administratively configured.  I will contend that *if* all
> the homenet boundary routers can automatically set a boundary based on
> getting a prefix delegation from an ISP, that satisfies the
> administratively configured rule 4291.
> 
> If the WG is agreeable with that, there are a few things I would like to
> see in the arch doc:
> 
> 1. References to site-local scope need to be changed to admin-scope
> 
> 2. Some guidance on the setting of that boundary triggered by an
> administrative function like PD is needed
> 
> Regards,
> Brian
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

v2.23.0 | Report a Bug | By Email