[ssm] ssm wg status update, ssm meeting in Minneapolis

Hugh Holbrook <holbrook@cisco.com> Mon, 13 October 2003 19:48 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23410 for <ssm-archive@lists.ietf.org>; Mon, 13 Oct 2003 15:48:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98ej-0004TA-9f; Mon, 13 Oct 2003 15:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98eG-0004Nj-2k for ssm@optimus.ietf.org; Mon, 13 Oct 2003 15:46:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23316 for <ssm@ietf.org>; Mon, 13 Oct 2003 15:46:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A98eE-0007PM-00 for ssm@ietf.org; Mon, 13 Oct 2003 15:46:30 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1A98eE-0007Om-00 for ssm@ietf.org; Mon, 13 Oct 2003 15:46:30 -0400
Received: from holbrook-laptop.cisco.com (dhcp-10-33-235-56.cisco.com [10.33.235.56]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h9DJjwvA023422; Mon, 13 Oct 2003 12:45:58 -0700 (PDT)
Received: by holbrook-laptop.cisco.com (Postfix, from userid 500) id 954F210B85C; Mon, 13 Oct 2003 12:46:56 -0700 (PDT)
From: Hugh Holbrook <holbrook@cisco.com>
To: ssm@ietf.org
Cc: holbrook@cisco.com, supratik@sprintlabs.com
Reply-To: holbrook@cisco.com
Message-Id: <20031013194656.954F210B85C@holbrook-laptop.cisco.com>
Date: Mon, 13 Oct 2003 12:46:56 -0700
Subject: [ssm] ssm wg status update, ssm meeting in Minneapolis
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>

The SSM working group has not met in quite some time.  Here's a status
update on our progress.

      - The informational overview draft is now an RFC.  Yay!

      - The ssm-arch draft is ready to advance to the IESG for
        consideration as an RFC, pending a discussion of the IPR issue
        mentioned in my previous mail.

      - The question of administratively scoped SSM addresses
        has come up numerous times: are they necessary, and if so,
        where should they be allocated.  There has been prior
        discussion on the list but no clear consensus has been reached
        on what to do.  I plan to submit an -00 draft on the
        admin-scoping topic in the next week which maybe can seed
        the discussion.


We think it would be worthwhile for the working group to meet in
Minneapolis to try to move toward consensus on the admin scoping issue
and possibly on the IPR issue.  So we're requesting a 1 hour slot at
the Minneapolis IETF (hopefully on Wednesday next to Magma).  Other
contributions and comments before Minneapolis are of course welcome.

SSM working group meeting tentative agenda:

    Admin scoping and SSM - what to do.
    (possibly) ssm-arch IPR issues

If you have more requests for agenda items, please send them to us.
    
Thanks,
-Hugh and Supratik


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm