IETF Logo Mail Archive

[Fwd: Re: draft-freed-sieve-in-xml status?]

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 15 December 2008 17:44 UTC

Return-Path: <owner-ietf-mta-filters@mail.imc.org>
X-Original-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Delivered-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27AFA3A683E for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Mon, 15 Dec 2008 09:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.638
X-Spam-Level:
X-Spam-Status: No, score=-2.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtXeyjnw2gDA for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Mon, 15 Dec 2008 09:44:19 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 350C33A6A44 for <sieve-archive-Aet6aiqu@ietf.org>; Mon, 15 Dec 2008 09:44:17 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mBFHRLGh040965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Dec 2008 10:27:21 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id mBFHRLfA040964; Mon, 15 Dec 2008 10:27:21 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mBFHR9gt040950 for <ietf-mta-filters@imc.org>; Mon, 15 Dec 2008 10:27:20 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.192] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SUaTbAB05ZPk@rufus.isode.com>; Mon, 15 Dec 2008 17:27:08 +0000
Message-ID: <4946933D.2040000@isode.com>
Date: Mon, 15 Dec 2008 17:26:21 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-mta-filters@imc.org
Subject: [Fwd: Re: draft-freed-sieve-in-xml status?]
Content-Type: multipart/mixed; boundary="------------070607050500080605020409"
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>

Forwarding to the mailing list with Ned's permission.
--- Begin Message --- 
Ned Freed wrote:

>
>> Can we just standardize a namespace URI (but don't require use of
>> namespaces) and be done with this issue?
>
>
> I have no objection as long as we don't clutter up the examples with 
> it. RFC
> 3470 has this to say about namespace usage in RFCs:
>
>  In the case of namespaces in IETF standards-track documents, it would be
>  useful if there were some permanent part of the IETF's own web space 
> that
>  could be used for this purpose. In lieu of such, other permanent URIs 
> can
>  be used, e.g., URNs in the IETF URN namespace (see [11] and [12]). 
> Although
>  there are instances of IETF specifications creating new URI schemes to
>  define XML namespaces, this practice is strongly discouraged.
>
> RFC 3688 then created the necessary allocation and an associated 
> registry:
>
>  ns -- XML Namespaces [W3C.REC-xml-names] are named by a URI. They 
> have no
>  real, machine-parseable representation. Thus, the registered document 
> will be
>  either the specification or a reference to it. In the case where a 
> URI is not
>  provided by the registrant, the IANA will assign a URN of the form
>  'urn:ietf:params:xml:ns:<id> which will be the XML Namespace's name.
>
> It is also expected that schemata will be registered. However, since 
> we're
> about to switch to Relax NG and AFAICT the schema registry is for
> XML Schema language stuff only, this won't apply to us as of the next
> revision. So we'll end up with an IANA Considerations section like the
> following:
>
> 7.  IANA Considerations
>
>   This section registers a new XML namespace per the procedures in RFC
>   3688 [RFC3688].
>
> URI:  urn:ietf:params:xml:ns:sieve
>
> Registrant Contact:  IETF Sieve working group <ietf-mta-filters@imc.org>
>
> XML:
>
>  BEGIN
>  <?xml version="1.0"?>
>  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
>    "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
>  <html xmlns="http://www.w3.org/1999/xhtml">
>  <head>
>    <meta http-equiv="content-type"
>          content="text/html;charset=iso-8859-1"/>
>    <title>Sieve Namespace</title>
>  </head>
>  <body>
>    <h1>Namespace for Sieve Language objects expressed in XML</h1>
>    <h2>urn:ietf:params:xml:ns:sieve</h2>
>    <p>See <a href="http://www.rfc-editor.org/rfc/rfc5361.txt">
>    RFC 5361</a>.
>    </p>
>  </body>
>  </html>
>  END
>
> Unless there are objections I'll include this in the next draft.

This looks good to me. Thanks!

BTW, my reply was directly to you. However I think your reply should go 
to the mailing list. Can you either forward your reply to the mailing 
list or can I do that?
--- End Message ---

v2.46.0 | Report a Bug | By Email | System Status