IETF Logo Mail Archive

Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88

James Polk <jmpolk@cisco.com> Thu, 16 January 2014 20:19 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B841ACC85 for <insipid@ietfa.amsl.com>; Thu, 16 Jan 2014 12:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level:
X-Spam-Status: No, score=-15.039 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.538, 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 oupy8B2eLswT for <insipid@ietfa.amsl.com>; Thu, 16 Jan 2014 12:19:40 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9905B1ACCD9 for <insipid@ietf.org>; Thu, 16 Jan 2014 12:19:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1156; q=dns/txt; s=iport; t=1389903567; x=1391113167; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=yere2T6s6zNyhy2nitalk5FQmziAWjqAlMLB24ObctU=; b=NzFqMr/TwurNrWp+ZNDKjV+SCuwADBNb1E6BO6JgkQrSqBlnyH9+E6Ba HOFl2+jDETkmQ4O7ngmq7SdXSvnL2v3YIw7/PUUdJemoTqfoLpUQMoX+7 cOKriOP2Qf2YKDPC7hdOBP5MrMT/lG09psgco4WjJr7vPKOg5JxEURj49 M=;
X-IronPort-AV: E=Sophos;i="4.95,669,1384300800"; d="scan'208";a="294830604"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 16 Jan 2014 20:19:26 +0000
Received: from jmpolk-WS.cisco.com ([10.89.8.188]) (authenticated bits=0) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0GKJQHH012866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 20:19:26 GMT
Message-Id: <201401162019.s0GKJQHH012866@rcdn-core2-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 16 Jan 2014 14:19:25 -0600
To: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D997394ABE4@VOEXM31W.internal .vodafone.com>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D997394ABE4@VOEXM31W.internal.vodafone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Authenticated-User: jmpolk
Cc: "DRAGE, Keith (Keith) (keith.drage@alcatel-lucent.com)" <keith.drage@alcatel-lucent.com>, "insipid@ietf.org" <insipid@ietf.org>, "Gonzalo Salgueiro (gsalguei@cisco.com)" <gsalguei@cisco.com>
Subject: Re: [Insipid] draft-dawes-dispatch-logme-reqs after IETF#88
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:19:41 -0000

Peter

To be blunt, if you seriously want this draft to be considered for 
INSIPID WG adoption you need to put "-insipid-" in the filename, and 
stop putting "-dispatch-" in the filename.

Linking the drafts is simple work for the chairs to do, if that's your concern.

James

At 11:31 AM 1/16/2014, Dawes, Peter, Vodafone Group wrote:
>Hello All,
>Following up from IETF#88 I have uploaded a revised logme 
>requirements draft (version -04).
>
>https://datatracker.ietf.org/doc/draft-dawes-dispatch-logme-reqs/
>
>As per the comments in Vancouver, version -04 does not include REQ9 
>regarding a logging server address and the related sub-clause 6.2.2. 
>Also, clause 7 on potential solutions has been removed. These 
>requirements seem to be stable now.
>
>I will upload a related solutions draft by the end of next week 
>(Friday 24) at the latest and I hope we can discuss solution options 
>here on the list and then later on at IETF#89 at the beginning of March.
>
>Regards,
>Peter
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid

v2.23.0 | Report a Bug | By Email