IETF Logo Mail Archive

Re: [SAM] [irsg] IRSG review for draft-irtf-samrg-sam-baseline-protocol-02

John Buford <buford@samrg.org> Wed, 01 May 2013 15:55 UTC

Return-Path: <buford@samrg.org>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87EF121F9A6B for <sam@ietfa.amsl.com>; Wed, 1 May 2013 08:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.07
X-Spam-Level:
X-Spam-Status: No, score=-100.07 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 31zlAXaRhVEo for <sam@ietfa.amsl.com>; Wed, 1 May 2013 08:55:48 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id BF54921F9A69 for <sam@irtf.org>; Wed, 1 May 2013 08:55:48 -0700 (PDT)
Received: (qmail 1037 invoked by uid 0); 1 May 2013 15:55:21 -0000
Received: from unknown (HELO host181.hostmonster.com) (74.220.207.181) by oproxy7.bluehost.com with SMTP; 1 May 2013 15:55:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=samrg.org; s=default; h=To:Date:Subject:From:Cc:Message-Id:Content-Transfer-Encoding:Content-Type:In-Reply-To:Mime-Version:References; bh=qc8vW28tttzNGcB6S9YO/p0WZz7ZZf4cIAE6tGv9Eec=; b=AeFAnXlVjUwzLD1ICb9S6bBXS13CMK45KOSlrQb/Odc2pZBnn7tjuGEudZs7yjDGTPV3IIaT+jnmcooVGhBtNP3Rb2ZKb9pa8ao/1KoI7OIBAgfq193G+T/0SwSdQN0c;
Received: from [198.228.206.87] (port=54435 helo=[10.16.115.220]) by host181.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <buford@samrg.org>) id 1UXZNJ-0001iF-4d; Wed, 01 May 2013 09:55:21 -0600
References: <0A9F560A-846B-40DC-83BB-DE85D7486606@ifi.uio.no> <4B1FBAB9-36C6-42B5-B976-6A156C72E432@ifi.uio.no> <517CD713.3060006@informatik.haw-hamburg.de> <0297C4A1-18B3-4485-AEF2-9D29667C3E5B@ifi.uio.no> <48E0C724888CBE47A7912FCEB14DF8F406F0E2@AZ-US1EXMB02.global.avaya.com> <1599A8CE-8979-426D-A208-44D8C6288687@ifi.uio.no> <1896D978-7B37-4902-8C63-0B60716C3F2E@netapp.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <1896D978-7B37-4902-8C63-0B60716C3F2E@netapp.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <473DFE40-C402-4A75-87CF-2157F005CCDD@samrg.org>
X-Mailer: iPad Mail (10B329)
From: John Buford <buford@samrg.org>
Date: Wed, 01 May 2013 11:58:53 -0400
To: "Eggert, Lars" <lars@netapp.com>
X-Identified-User: {2055:host181.hostmonster.com:samrgorg:samrg.org} {sentby:smtp auth 198.228.206.87 authed with buford@samrg.org}
Cc: "sam@irtf.org" <sam@irtf.org>, Michael Welzl <michawe@ifi.uio.no>, Internet Research Steering Group <irsg@irtf.org>
Subject: Re: [SAM] [irsg] IRSG review for draft-irtf-samrg-sam-baseline-protocol-02
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 15:55:53 -0000

Thanks for the pointer.   It does seem then that experimental would be more accurate.

Can we change that after the formal poll ends or should we change it now?

John

Sent from my iPad

On May 1, 2013, at 11:28 AM, "Eggert, Lars" <lars@netapp.com> wrote:

> On May 1, 2013, at 16:58, Michael Welzl <michawe@ifi.uio.no> wrote:
>> Not sure that's needed?!
>> http://www.ietf.org/iesg/informational-vs-experimental.html doesn't say anything about requiring an implementation, unless I missed it
> 
> It's not needed. Pick whatever seems most appropriate.
> 
> (The IETF rules at the URL above are a good guideline, but don't actually apply to the I*R*TF.)
> 
> Lars

v2.23.0 | Report a Bug | By Email