[apps-discuss] Feedback on draft-moonesamy-rfc2919bis-01

S Moonesamy <sm+ietf@elandsys.com> Sat, 21 January 2012 00:00 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2AA21F86DA for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jan 2012 16:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level:
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, 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 pWf2oXcaGV7v for <apps-discuss@ietfa.amsl.com>; Fri, 20 Jan 2012 16:00:53 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E592821F869D for <apps-discuss@ietf.org>; Fri, 20 Jan 2012 16:00:52 -0800 (PST)
Received: from SUBMAN.elandsys.com ([41.136.235.213]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q0L00aoT004034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Fri, 20 Jan 2012 16:00:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1327104048; i=@elandsys.com; bh=XvdvCm/r8Yfd9vSb9iIWmcZ76xK/+CoiSPv15gVSebg=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=Zzlk+BzmKKBXOWFjf6M7v5llYheblilPIMx9Tc9H+2Y7PHuQNVa0pw2JaJTiZwMx/ E/7Y73PzTsUdrQVCFABLB9JtOGlDzfd5O9u2W7qzwspGcvkQqk45ovxTs0WqDPaeZo ObVaBpXP2ddX35uNuUTIuJz4TexzOzGX6xtqS05c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1327104048; i=@elandsys.com; bh=XvdvCm/r8Yfd9vSb9iIWmcZ76xK/+CoiSPv15gVSebg=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=vh6w11YE0JymCTuSBgHb/XmjAwLYsUgUmCx9vkp+Je5d5J1lhEUCtSuaVUaf3pHWW owEcweW1ITcWLB16zUErvNocN+W84W/fGPPyfHEaxAE5NixXM1xTvqYf71pqZh919H ekGZ4U36/8lQ7SacSUMlodzVO6SICaGmk/qDOcAQ=
Message-Id: <6.2.5.6.2.20120120145614.09414138@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 20 Jan 2012 15:40:34 -0800
To: apps-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [apps-discuss] Feedback on draft-moonesamy-rfc2919bis-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jan 2012 00:00:55 -0000

Hello,

I moved the List-Sequence header field from 2369bis to 
draft-moonesamy-rfc2919bis-02 after discussing about the drafts with 
Grant Neufeld.  I'll submit the revision in a few days.

Murray S. Kucherawy [1] [2] commented on the purpose of Appendix 
A.1.  I will be making the following change:

   A popular feature of some MLMs is the "tagging" of the Subject header field
   by prefixing the header field's contents with the name of the mailing list,
   e.g. "[example]" for a list called "example".  The difference between a List
   Identifier and a subject tag is that while a List Identifier is unique,
   a subject tag is usually the short form of a mailing list's name.
   Such a namespace is inherently flat, unmanaged and thus non-unique.

I removed the text in Section 6 about case-insensitive string 
comparison.  Murray also commented on the switch from "localhost" to 
"invalid" and I responded to the comment [3].

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg04039.html
2. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg04049.html
3. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg04040.html