From owner-ietf@ietf.org  Sun Feb  2 13:47:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10321;
	Sun, 2 Feb 2003 13:47:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fOwM-0007DO-00
	for ietf-list@ran.ietf.org; Sun, 02 Feb 2003 13:34:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fOvl-0007D1-00
	for ietf@ran.ietf.org; Sun, 02 Feb 2003 13:33:25 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10134;
	Sun, 2 Feb 2003 13:29:06 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6A979622AC; Sun,  2 Feb 2003 19:32:39 +0100 (CET)
Date: Sun, 02 Feb 2003 10:03:10 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Cc: iesg@ietf.org
Subject: Whether we should require "IETF consensus"
Message-ID: <164789654.1044180190@localhost>
In-Reply-To: <20030130103107.305bb5fd.moore@cs.utk.edu>
References: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
 	<1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
 <20030130103107.305bb5fd.moore@cs.utk.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Attempting to untangle some threads on this rather divergent debate....

We seem to have three different discussions going:

A - Is the IESG allowed to block publication of internet-drafts as RFCs if 
they make assignment in IANA registers where the rule for registration is 
"IETF Consensus", and the IESG determines that the IETF consensus is not 
satisfied?

B - What review process must the IESG take before taking the action to 
block or allow publication of such an internet-draft (ie "what does IETF 
Consensus mean")?

C - Given the debate about the specific documents, should the IESG have 
approved draft-aboulmagd-ccamp-crldp-ason-ext for publication?

To my mind, the answer to the first question is clearly YES.
When RFC 2434 was written, the "IETF Consensus" category was created 
because there were cases where any kind of "free-for-all" assignment was 
deemed harmful to the Internet - because of confusion, "name homesteading", 
resource depletion or too easy "labeled non-interoperability", or for other 
reasons - while each individual registration might be not important enough 
to warrant standards-track processing, be under the control of some other 
body, or be inappropriate for standards-track for other reasons.

There is clear, demonstrable harm to the Internet in these cases - in some 
cases, not in the individual request, but in the aggregate. The "IETF 
Consensus" mechanism is a tool that the community can use to give the IESG 
the power to defend the Internet against such harm. And the community has 
used it, as witnessed by the many documents using this mechanism.

The IANA follows the RFC-documented instructions on when to insert values 
into its registries, and IESG instructions on "IETF Consensus" registries.

Having a situation where an RFC documents something at variance with IANA 
registration seems absurd, so it seems unreasonable to me that the RFC 
Editor would publish an RFC documenting such an assignment, given that the 
IESG made the RFC Editor aware of the situation.
(Of course, that makes the position of RFC 2882, "extended RADIUS 
practices", which documents codes in use but not registered with the IANA, 
slightly absurd. We need to fix that, too....)

Rather than attacking the 2 other issues in the same mail, I'll follow up 
the second one in another message, and mainly leave the third one to 
subject matter experts - hopefully allowing us to untangle the abstract 
issues from the specific one....

                   Harald





From owner-ietf@ietf.org  Sun Feb  2 13:47:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10344;
	Sun, 2 Feb 2003 13:47:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fOwM-0007DU-00
	for ietf-list@ran.ietf.org; Sun, 02 Feb 2003 13:34:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fOvo-0007D3-00
	for ietf@ran.ietf.org; Sun, 02 Feb 2003 13:33:28 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10143;
	Sun, 2 Feb 2003 13:29:08 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 19E816238A; Sun,  2 Feb 2003 19:32:42 +0100 (CET)
Date: Sun, 02 Feb 2003 10:30:09 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: IETF <ietf@ietf.org>
Cc: iesg@ietf.org, poised@lists.tislabs.com
Subject: What review is required for "IETF Consensus"?
Message-ID: <166408723.1044181809@localhost>
In-Reply-To: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com>
References:  <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thread B from my previous message..... this is being CCed to the POISED 
list, for reasons that may be obvious after reading the message; for POISED 
subscribers - this is followup to an IETF list thread.

Question:

What review process must the IESG take before taking the action to block or 
allow publication of such an internet-draft (ie "what does IETF Consensus 
mean")?

This is not written in RFC 2434.
Some tactics that have been used in the past to gather information for the 
IESG's decision include:

- "It's obviously OK". Approved WG document, or competently written 
documentation from subject matter experts, reviewed by people with 
competence on the specific registry. The IESG looks at it and thinks that 
it's obvioiusly right. Example: application/ogg, documented in 
draft-walleij-ogg-mediatype.

- Subject matter expert group review. For instance, posting to the DHC WG 
asking for opinions on a DHCP extension. WG chairs' feedback will carry a 
lot of weight.

- IETF Last Call for Informational/Experimental, with the IESG evaluating 
the feedback.

In all cases, the IESG has to evaluate; there's no other established body 
to do it. "The buck stops here".

Among the cases to consider:

- Everyone approves. Go for it.

- Nobody cares. No comments; the IESG will usually decide that nobody saw 
any looming danger to the Internet, and allow the registration.

- Serious objections. The comments clearly indicate that the registration 
would be harmful to the Internet (and how), and the IESG agrees with that 
evaluation. The IESG will refuse.

- Incompetent or incomplete document. The IESG will usually object to this 
on its own - without documentation clear enough to determine whether this 
is OK or harmful, it would be remiss of the IESG to let the document go 
forward even to an IETF Last Call.
We can't claim IETF consensus on something we can't understand.

- Dissension within the IETF. Like in the case of a WG, the IESG has to 
evaluate the arguments on their merits; obviously the proposers think that 
the registration should be allowed, and opposition without a rational basis 
should no more be allowed to block this registration than it should be 
allowed to block WG progress. But as the saying goes - "this is why you get 
the big bucks".
Among the things to consider here is that the determination must be made in 
a timely fashion - sometimes there are reasons why letting debate rage for 
another 6 months doesn't seem like an attractive option.

Questions for the audience:

- should this description, or something like it, go into 
draft-iesg-procedures?
- are there guidelines that the IESG should use when trying to determine 
the right outcome in the "dissension" case?
- does this debate belong on the POISED list, together with the discussion 
of the IESG charter and the IESG procedures?

Thoughts?

                 Harald








From owner-ietf@ietf.org  Mon Feb  3 00:35:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19058;
	Mon, 3 Feb 2003 00:35:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fZBD-00049h-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 00:30:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fZAE-00049N-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 00:29:02 -0500
Received: from fsnt.future.futsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18880
	for <ietf@ietf.org>; Mon, 3 Feb 2003 00:24:35 -0500 (EST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004337731@fsnt.future.futsoft.com> for <ietf@ietf.org>;
 Mon, 03 Feb 2003 11:03:27 +0530
Received: from ramanad (ramanad.future.futsoft.com [10.8.3.18])
	by kailash.future.futsoft.com (8.12.2/8.12.2) with SMTP id h135POJN017228
	for <ietf@ietf.org>; Mon, 3 Feb 2003 10:55:24 +0530
Reply-To: <ramanad@future.futsoft.com>
From: "ramanad" <ramanad@future.futsoft.com>
To: <ietf@ietf.org>
Subject: IPHC RFC2507 clarification
Date: Mon, 3 Feb 2003 10:55:29 +0530
Message-Id: <000801c2cb44$ab159c10$1203080a@ramanad>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <136220000.1038313442@askvoll.hjemme.alvestrand.no>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
I am working on IPHC RFC 2507.I need small clarification regarding

1).
Section 6 b) ( RFC 2507, IPHC page 21)

COMPRESSED_TCP_NODELTA header format:

+------------+
+   CID      +
+------------+
+ RANDOM fields ,if any
+---------------
+ Whole TCP header except port numbers
+-----------------

Consider the following two cases:
Case1: IPv4 header with 'Options'.In this case all the fields in IPv4 header
are 'RANDOM'.
Case2: IPv4 header with out 'Options'.In this case onle 'IP_IDentifier' in
IPv4 header is 'RANDOM'.

How the decompressor will distinguish the above two?
Is the only length of the packet is the deciding parameter?

2).
Sections 5.3.1 and 5.3.2 ( RFC 2507, IPHC page 19).
I am using first length field to send CID. Here I have basic confusion, I am
assuming the given format in sections 5.3.1 and 5.3.2 are Host byte order.
So I am filling this field in Network order ( i.e. please see below fig for
example) in
FULL HEADERS. Is it correct?

Given in RFC 2507 as follows:
+------------+-----------+
+  Pkt Nr    +   CID     +
+------------+-----------+

It will be filled as follows in FULL HEADERS ( To make it in Network Order)
+------------+-----------+
+   CID      +  Pkt Nr   +
+------------+-----------+

Please correct me if I am doing wrong?

Thanks in advance.

Regards,
Ramana.



***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************



From owner-ietf@ietf.org  Mon Feb  3 09:54:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09009;
	Mon, 3 Feb 2003 09:54:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fhy8-00055u-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 09:53:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fXFu-0002pE-00
	for ietf@ran.ietf.org; Sun, 02 Feb 2003 22:26:46 -0500
Received: from blount.mail.mindspring.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17209;
	Sun, 2 Feb 2003 22:22:20 -0500 (EST)
Received: from dialup-64.157.125.232.dial1.dallas1.level3.net ([64.157.125.232] helo=ix.netcom.com)
	by blount.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 18fXF0-0007Nj-00; Sun, 02 Feb 2003 22:25:51 -0500
Message-ID: <3E3DFDA8.4F50DD55@ix.netcom.com>
Date: Sun, 02 Feb 2003 21:27:05 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@Alvestrand.no>
CC: IETF <ietf@ietf.org>, iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: What review is required for "IETF Consensus"?
References: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com> <166408723.1044181809@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald and all,

  I "Guess" that a IETF consensus really means whatever you Harald
says it means much like what consensus meant while you were
Chair of the DNSO GA.  But to be honest, no consensus can be
determined unless it is measured, which means a VOTE must be
held amongst IETF participants.  Perish the thought, eh Harald?!  >;)

Harald Tveit Alvestrand wrote:

> Thread B from my previous message..... this is being CCed to the POISED
> list, for reasons that may be obvious after reading the message; for POISED
> subscribers - this is followup to an IETF list thread.
>
> Question:
>
> What review process must the IESG take before taking the action to block or
> allow publication of such an internet-draft (ie "what does IETF Consensus
> mean")?
>
> This is not written in RFC 2434.
> Some tactics that have been used in the past to gather information for the
> IESG's decision include:
>
> - "It's obviously OK". Approved WG document, or competently written
> documentation from subject matter experts, reviewed by people with
> competence on the specific registry. The IESG looks at it and thinks that
> it's obvioiusly right. Example: application/ogg, documented in
> draft-walleij-ogg-mediatype.
>
> - Subject matter expert group review. For instance, posting to the DHC WG
> asking for opinions on a DHCP extension. WG chairs' feedback will carry a
> lot of weight.
>
> - IETF Last Call for Informational/Experimental, with the IESG evaluating
> the feedback.
>
> In all cases, the IESG has to evaluate; there's no other established body
> to do it. "The buck stops here".
>
> Among the cases to consider:
>
> - Everyone approves. Go for it.
>
> - Nobody cares. No comments; the IESG will usually decide that nobody saw
> any looming danger to the Internet, and allow the registration.
>
> - Serious objections. The comments clearly indicate that the registration
> would be harmful to the Internet (and how), and the IESG agrees with that
> evaluation. The IESG will refuse.
>
> - Incompetent or incomplete document. The IESG will usually object to this
> on its own - without documentation clear enough to determine whether this
> is OK or harmful, it would be remiss of the IESG to let the document go
> forward even to an IETF Last Call.
> We can't claim IETF consensus on something we can't understand.
>
> - Dissension within the IETF. Like in the case of a WG, the IESG has to
> evaluate the arguments on their merits; obviously the proposers think that
> the registration should be allowed, and opposition without a rational basis
> should no more be allowed to block this registration than it should be
> allowed to block WG progress. But as the saying goes - "this is why you get
> the big bucks".
> Among the things to consider here is that the determination must be made in
> a timely fashion - sometimes there are reasons why letting debate rage for
> another 6 months doesn't seem like an attractive option.
>
> Questions for the audience:
>
> - should this description, or something like it, go into
> draft-iesg-procedures?
> - are there guidelines that the IESG should use when trying to determine
> the right outcome in the "dissension" case?
> - does this debate belong on the POISED list, together with the discussion
> of the IESG charter and the IESG procedures?
>
> Thoughts?
>
>                  Harald

Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
================================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 214-244-4827 or 214-244-3801







From owner-ietf@ietf.org  Mon Feb  3 09:55:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09034;
	Mon, 3 Feb 2003 09:55:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fhy8-00056M-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 09:53:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fd1x-00078C-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 04:36:45 -0500
Received: from verdi.jlc.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01483;
	Mon, 3 Feb 2003 04:32:16 -0500 (EST)
Received: by verdi.jlc.net (Postfix, from userid 104)
	id 075A23379A; Mon,  3 Feb 2003 04:35:51 -0500 (EST)
Date: Mon, 3 Feb 2003 04:35:51 -0500
From: John Leslie <john@jlc.net>
To: Harald Tveit Alvestrand <harald@Alvestrand.no>
Cc: IETF <ietf@ietf.org>, iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: What review is required for "IETF Consensus"?
Message-ID: <20030203043551.N7309@verdi>
References: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com> <166408723.1044181809@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <166408723.1044181809@localhost>; from harald@Alvestrand.no on Sun, Feb 02, 2003 at 10:30:09AM -0800
Sender: owner-ietf@ietf.org
Precedence: bulk

   I must admit to some confusion about what Harald is asking for.

   The context here is discussion of RFC 2434 "Guidelines for Writing
an IANA Considerations Section" (BCP 26). We're discussing "example"
policies for IANA assignments. Specifically there is:

" IETF Consensus - New values are assigned through the IETF consensus
" process. Specifically, new assignments are made via RFCs approved by
" the IESG. Typically, the IESG will seek input on prospective assignments
" from appropriate persons (e.g., a relevant Working Group if one exists).

which requires publication of an RFC, and

" IESG Approval - New assignments must be approved by the IESG, but
" there is no requirement that the request be documented in an RFC
" (though the IESG has discretion to request documents or other
" supporting materials on a case-by-case basis).

   I think Harald is asking for comments on this.

Harald Tveit Alvestrand <harald@Alvestrand.no> wrote:
> 
> Question:
> 
> What review process must the IESG take before taking the action to block or 
> allow publication of such an internet-draft (ie "what does IETF Consensus 
> mean")?
> 
> This is not written in RFC 2434.

   I read this section of RFC 2434 as an escape hatch, not as a regular
process.

   Before I can intelligently discuss the "process" for "IESG Approval",
I need some justification of why this option is used at all. It strikes
me as decidedly unwise to make a permanent IANA assignment based upon
an Internet Draft (which by definition expires in six months).

> Some tactics that have been used in the past to gather information for the 
> IESG's decision include:
> 
> - "It's obviously OK". Approved WG document, or competently written 
> documentation from subject matter experts, reviewed by people with 
> competence on the specific registry. The IESG looks at it and thinks that 
> it's obvioiusly right. Example: application/ogg, documented in 
> draft-walleij-ogg-mediatype.

   Well, immediately we are struck with the question, _which_
draft-walleij-ogg-mediatype. I believe draft-walleij-ogg-mediatype.08
is current.

   Granted, I have no reason to believe the IANA assignment has
changed or will change; and the actual registration is minimal:

" To: ietf-types@iana.org
" Subject: Registration of MIME media type application/ogg
" MIME media type name: application
" MIME subtype name: ogg
" Required parameters: none
" Optional parameters: none
" Encoding Considerations: ...
" Security Considerations: ...
" Interoperability considerations: ..
" Published specification: See [1]

where [1] is:

" [1]  Pfeiffer, S., "The Ogg encapsulation format version 0",
"      Internet-Draft XXXX, November 2002.

   There's the problem: We've got an unquestionably useful format
depending on a document which will expire in May. IMHO, this richly
deserves an RFC (which doesn't expire).

> - Subject matter expert group review. For instance, posting to the DHC WG 
> asking for opinions on a DHCP extension. WG chairs' feedback will carry a 
> lot of weight.

   This is a limited case, where the appropriate WG is still active.
Clearly the WG Chair is the appropriate judge of WG consensus. But the
documentation is always in danger of being too sparse...

> - IETF Last Call for Informational/Experimental, with the IESG evaluating 
> the feedback.

   Isn't that an RFC?

> In all cases, the IESG has to evaluate; there's no other established body 
> to do it. "The buck stops here".
> 
> Among the cases to consider:
> 
> - Everyone approves. Go for it.
> 
> - Nobody cares. No comments; the IESG will usually decide that nobody saw 
> any looming danger to the Internet, and allow the registration.

   So long as there's no imminent danger of exhaustion of the name space,
and the documentation is adequate, I agree.

> - Serious objections. The comments clearly indicate that the registration 
> would be harmful to the Internet (and how), and the IESG agrees with that 
> evaluation. The IESG will refuse.
> 
> - Incompetent or incomplete document. The IESG will usually object to this 
> on its own - without documentation clear enough to determine whether this 
> is OK or harmful, it would be remiss of the IESG to let the document go 
> forward even to an IETF Last Call.
> We can't claim IETF consensus on something we can't understand.

   Technically, we're not talking about "IETF consensus" ...

   However, "IESG Approval" certainly _should_ imply that the IESG
_understands_ the registration request.

> - Dissension within the IETF. Like in the case of a WG, the IESG has to 
> evaluate the arguments on their merits; obviously the proposers think
> that the registration should be allowed, and opposition without a
> rational basis should no more be allowed to block this registration
> than it should be allowed to block WG progress. But as the saying goes
> - "this is why you get the big bucks".

   Did I miss the part where your salary was increased?

> Among the things to consider here is that the determination must be made
> in a timely fashion - sometimes there are reasons why letting debate
> rage for another 6 months doesn't seem like an attractive option.

   So often, when "time is of the essence", it means that the person(s)
preparing the request _chose_ not to allow sufficient time. This sort
of behavior should NOT be rewarded.

   That said, "letting debate rage for another 6 months" isn't the
right solution either. Clearly defining the issue to be resolved is
the best policy, followed by careful reading (and possible feedback)
of the documentation which ensues.

> Questions for the audience:
> 
> - should this description, or something like it, go into 
> draft-iesg-procedures?

   I'm not convinced. I still think we're talking about an escape hatch,
not the "normal" process.

> - are there guidelines that the IESG should use when trying to determine 
> the right outcome in the "dissension" case?

   Minimize your work!
   Demand clear documentation.

> - does this debate belong on the POISED list, together with the discussion 
> of the IESG charter and the IESG procedures?

   Seems reasonable to me...

--
John Leslie <john@jlc.net>





From owner-ietf@ietf.org  Mon Feb  3 09:55:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09046;
	Mon, 3 Feb 2003 09:55:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fhwC-00051d-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 09:51:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18en2a-00050P-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 21:05:56 -0500
Received: from carmen.ipv6.tilab.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24902
	for <ietf@ietf.org>; Fri, 31 Jan 2003 21:02:03 -0500 (EST)
Received: from carmen.ipv6.tilab.com (localhost [IPv6:::1])
	by carmen.ipv6.tilab.com (8.12.3/8.12.3) with ESMTP id h112306G026777
	for <ietf@ietf.org>; Sat, 1 Feb 2003 03:03:00 +0100 (MET)
Received: (from root@localhost)
	by carmen.ipv6.tilab.com (8.12.3/8.12.3/Submit) id h11230aW026776
	for ietf@ietf.org; Sat, 1 Feb 2003 03:03:00 +0100 (MET)
Date: Sat, 1 Feb 2003 03:03:00 +0100 (MET)
From: Super-User <root@carmen.ipv6.tilab.com>
Message-Id: <200302010203.h11230aW026776@carmen.ipv6.tilab.com>
To: ietf@ietf.org
Subject: The IETF_Censored mailing list
Sender: owner-ietf@ietf.org
Precedence: bulk


                        The IETF_Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf_censored@carmen.ipv6.cselt.it".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Raffaele D'Albenzio, irrelevant
   to the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
     * Some "out-of-office-reply" messages
       
   To join the list, send the word "subscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   To unsubscribe, send the word "unsubscribe" in the BODY of a message
   to ietf_censored-request@carmen.ipv6.cselt.it. Do not send to the list
   - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf_censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf_censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf_censored-rejects@carmen.ipv6.cselt.it - subscribe in the same
   fashion, by mail to ietf_censored-rejects-request@carmen.ipv6.cselt.it
   
   By public request, the current set of filters are listed at
   http://vesuvio.ipv6.tilab.com/cgi-bin/ietf_censored-filters
   
   This page is http://carmen.ipv6.cselt.it/ietf_censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Raffaele D'Albenzio < root@carmen.ipv6.cselt.it>





From owner-ietf@ietf.org  Mon Feb  3 13:58:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17383;
	Mon, 3 Feb 2003 13:58:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18flau-0004Ux-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 13:45:24 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fla9-0004TR-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 13:44:37 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16855
	for <ietf@ietf.org>; Mon, 3 Feb 2003 13:40:02 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 4CBE7621FB
	for <ietf@ietf.org>; Mon,  3 Feb 2003 19:43:32 +0100 (CET)
Date: Mon, 03 Feb 2003 10:41:34 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Information on Directorates and Finances
Message-ID: <253493554.1044268894@localhost>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have put two web pages up at the following URL:

http://www.ietf.org/u/chair/

One details the directorates that currently exist in the IETF, with 
memberships of most of them.

The other one is the IETF finances for 2001.

The presentation format is subject to modification - if you find things 
unclear or hard to understand, drop me a line!

                        Harald




From owner-ietf@ietf.org  Mon Feb  3 14:35:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18551;
	Mon, 3 Feb 2003 14:35:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fmN8-0006NG-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 14:35:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fmMT-0006Lr-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 14:34:33 -0500
Received: from bean.ar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18373
	for <ietf@ietf.org>; Mon, 3 Feb 2003 14:29:59 -0500 (EST)
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h13JXXmn001597;
	Mon, 3 Feb 2003 11:33:33 -0800 (PST)
Date: Mon, 3 Feb 2003 11:33:36 -0800 (PST)
From: Rick Wesson <wessorh@ar.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: <ietf@ietf.org>
Subject: Re: Information on Directorates and Finances
In-Reply-To: <253493554.1044268894@localhost>
Message-ID: <Pine.LNX.4.33.0302031132310.7260-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Harald,

I'd never seen any finances for the ietf, but are these from 2002 or did
it just take that long to pull 2001 expenses together?

-rick


On Mon, 3 Feb 2003, Harald Tveit Alvestrand wrote:

> I have put two web pages up at the following URL:
>
> http://www.ietf.org/u/chair/
>
> One details the directorates that currently exist in the IETF, with
> memberships of most of them.
>
> The other one is the IETF finances for 2001.
>
> The presentation format is subject to modification - if you find things
> unclear or hard to understand, drop me a line!
>
>                         Harald
>
>




From owner-ietf@ietf.org  Mon Feb  3 15:32:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20644;
	Mon, 3 Feb 2003 15:32:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fnEM-0000WV-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 15:30:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fnE6-0000Ut-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 15:29:58 -0500
Received: from bean.ar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20430
	for <ietf@ietf.org>; Mon, 3 Feb 2003 15:25:23 -0500 (EST)
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h13KSxmn007393
	for <ietf@ietf.org>; Mon, 3 Feb 2003 12:28:59 -0800 (PST)
Date: Mon, 3 Feb 2003 12:29:02 -0800 (PST)
From: Rick Wesson <wessorh@ar.com>
To: <ietf@ietf.org>
Subject: sole-sourceing IANA function to ICANN for next 3 years
Message-ID: <Pine.LNX.4.33.0302031227240.7260-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


FYI

-rick

---------- Forwarded message ----------
Date: Mon, 3 Feb 2003 14:15:30 -0500
Subject: FW: US Grants ICANN Extension of Global Domain Powers

US Grants ICANN Extension of Global Domain Powers

By Kevin Murphy


ICANN, which manages policy aspects of the internet's domain name system, is
to be granted a three-year extension of its powers to manage the world's
country-code domain names, ComputerWire has learned.


The US Department of Commerce last week quietly published a document
detailing its decision to "sole-source" the contract for the so-called IANA
function to ICANN, as opposed to opening the contract for competitive
bidding.


ICANN and a spokesperson for the DoC's National Telecommunications and
Information Administration both confirmed the extension, although ICANN
general counsel Louis Touton added that no contract has yet been signed.


IANA is responsible for maintaining the definitive list of which
organizations, individuals, and domain servers are associated with
approximately 240 country-code top-level domains (ccTLDs), such as .uk, .us,
and .fr.


The decision will cause concern to some in the international community,
particularly those concerned in the policy aspects of the ccTLD industry.
Some ccTLD operators had considered a counter-bid for the IANA contract
before its March expiration.


A statement buried six clicks into a Federal web site heavily suggests that
the ICANN-DoC Memorandum of Understanding (MoU) and the IANA contract are
essentially inseparable, and that ICANN is the only party fit to run IANA.


The NTIA document said that ICANN, having assumed "key resources and
associated privatization responsibilities under the MoU" is therefore the
"only responsible entity that can continue to provide seamless performance
of the IANA functions".


As a further link, the three-year IANA contract will come up for renewal at
periods of six months, one year, one year, and six months - paced to
coincide exactly with the times the MoU comes up for renewal, Touton and the
NTIA said.


ICANN's Touton added that the decision was made because of how closely
linked the policy-making functions of ICANN are with the policy-implementing
functions of IANA, and that it "wouldn't make sense" for a third party to
take over IANA.


ICANN has been accused in the past of using the IANA function to further its
own ends. One of the Herculean tasks in the MoU requires ICANN to sign
stable operating agreements with each of the ccTLD operators, but this has
proved difficult.


In the majority of the cases when ICANN has signed such an agreement, it has
coincided with the re-delegation of a ccTLD to a new operator. The most
recent such deal was with the new government of Afghanistan.


Last October, a number of ccTLDs, disgruntled with their treatment by ICANN
over the four years of its existence, said they would consider mounting a
bid to take over the IANA function, being the groups most affected by its
decisions.


But the current international political climate would have made the US
venturing outside its borders for a contractor unlikely. Recent
denial-of-service attacks against the DNS root servers has created a mindset
among some where the DNS is a US national, rather than international,
resource that must be protected against "terrorism" like any physical
target.

Lisette Zarnowski
Register.com, Inc.
Manager, Public Relations/Special Events
(212) 798-9165
lzarnowski@register.com <mailto:tprohigh@register.com>

  <http://216.21.229.207/images/sig_line.gif>
  <http://216.21.229.207/images/sig_txt.gif>
<http://216.21.229.207/images/spacer.gif>

  <http://216.21.229.207/images/sig_logo.gif>
  <http://216.21.229.207/images/sig_line.gif>












From owner-ietf@ietf.org  Mon Feb  3 16:52:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22941;
	Mon, 3 Feb 2003 16:52:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18foTm-0005G1-00
	for ietf-list@ran.ietf.org; Mon, 03 Feb 2003 16:50:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18foTO-0005Eh-00
	for ietf@ran.ietf.org; Mon, 03 Feb 2003 16:49:50 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22786
	for <ietf@ietf.org>; Mon, 3 Feb 2003 16:45:13 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 74541621FB; Mon,  3 Feb 2003 22:48:49 +0100 (CET)
Date: Mon, 03 Feb 2003 13:24:05 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Rick Wesson <wessorh@ar.com>
Cc: ietf@ietf.org
Subject: Re: Information on Directorates and Finances
Message-ID: <263243944.1044278645@localhost>
In-Reply-To: <Pine.LNX.4.33.0302031132310.7260-100000@flash.ar.com>
References:  <Pine.LNX.4.33.0302031132310.7260-100000@flash.ar.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 3. februar 2003 11:33 -0800 Rick Wesson <wessorh@ar.com> wrote:

> Harald,
>
> I'd never seen any finances for the ietf, but are these from 2002 or did
> it just take that long to pull 2001 expenses together?
>

these are from 2001. It's been on my TODO list to get them on a web page 
forever, but I didn't get around to it before now.
I did a presentation on the same type of numbers in London (for 2000), but 
only in summary form, and it doesn't seem that I remembered to do one in 
Yokohama.
Now that I've done it once, I think the 2002 figures will be much faster....

                    Harald

> -rick
>
>
> On Mon, 3 Feb 2003, Harald Tveit Alvestrand wrote:
>
>> I have put two web pages up at the following URL:
>>
>> http://www.ietf.org/u/chair/
>>
>> One details the directorates that currently exist in the IETF, with
>> memberships of most of them.
>>
>> The other one is the IETF finances for 2001.
>>
>> The presentation format is subject to modification - if you find things
>> unclear or hard to understand, drop me a line!
>>
>>                         Harald
>>
>>
>
>
>





From owner-ietf@ietf.org  Tue Feb  4 00:14:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00463;
	Tue, 4 Feb 2003 00:14:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fvKV-0002fx-00
	for ietf-list@ran.ietf.org; Tue, 04 Feb 2003 00:09:07 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fvJr-0002eW-00
	for ietf@ran.ietf.org; Tue, 04 Feb 2003 00:08:27 -0500
Received: from nit.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00233
	for <ietf@ietf.org>; Tue, 4 Feb 2003 00:03:45 -0500 (EST)
Received: (from falk@localhost)
	by nit.isi.edu (8.11.6/8.11.6) id h1457Kw13021;
	Mon, 3 Feb 2003 21:07:20 -0800
Date: Mon, 3 Feb 2003 21:07:20 -0800
From: Aaron Falk <falk@isi.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Information on Directorates and Finances
Message-ID: <20030204050720.GC13444@isi.edu>
Mail-Followup-To: Harald Tveit Alvestrand <harald@alvestrand.no>,
	ietf@ietf.org
References: <253493554.1044268894@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <253493554.1044268894@localhost>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

Well done, Harald!  I applaud this move towards 'transparency.'  

One question.  In the sentence on the finance page where you wrote: 

  "In the US, this is one way in which hotels recover the cost of
  meeting rooms; in one recent query, the secretariat got a quote on
  meeting rooms without food for USD 238.000 (at 50% off list
  price). At a similar meeting where we got the meeting rooms for
  free, our food and beverages bill was approximately USD 250.000."

I'm a little confused as to whether the decimal has been substituted
for a comma or whether it's just in the wrong place or both.

--aaron

Harald Tveit Alvestrand wrote:
> I have put two web pages up at the following URL:
> 
> http://www.ietf.org/u/chair/
> 
> One details the directorates that currently exist in the IETF, with 
> memberships of most of them.
> 
> The other one is the IETF finances for 2001.
> 
> The presentation format is subject to modification - if you find things 
> unclear or hard to understand, drop me a line!
> 
>                        Harald
> 
> 
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which 
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on 
> what to pass are made solely by Raffaele D'Albenzio.



From owner-ietf@ietf.org  Tue Feb  4 01:18:05 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01822;
	Tue, 4 Feb 2003 01:18:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fwNN-0004h0-00
	for ietf-list@ran.ietf.org; Tue, 04 Feb 2003 01:16:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fwMh-0004fe-00
	for ietf@ran.ietf.org; Tue, 04 Feb 2003 01:15:27 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01709
	for <ietf@ietf.org>; Tue, 4 Feb 2003 01:10:46 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 50D5062573; Tue,  4 Feb 2003 07:14:14 +0100 (CET)
Date: Mon, 03 Feb 2003 22:12:51 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Aaron Falk <falk@isi.edu>
Cc: ietf@ietf.org
Subject: Re: Information on Directorates and Finances
Message-ID: <294970374.1044310371@localhost>
In-Reply-To: <20030204050720.GC13444@isi.edu>
References: <253493554.1044268894@localhost>
 <20030204050720.GC13444@isi.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 3. februar 2003 21:07 -0800 Aaron Falk <falk@isi.edu> wrote:

> Well done, Harald!  I applaud this move towards 'transparency.'
>
> One question.  In the sentence on the finance page where you wrote:
>
>   "In the US, this is one way in which hotels recover the cost of
>   meeting rooms; in one recent query, the secretariat got a quote on
>   meeting rooms without food for USD 238.000 (at 50% off list
>   price). At a similar meeting where we got the meeting rooms for
>   free, our food and beverages bill was approximately USD 250.000."
>
> I'm a little confused as to whether the decimal has been substituted
> for a comma or whether it's just in the wrong place or both.

It's just my Norwegian decimals.... both numbers are in the ballpark of a 
quarter million dollars.
(Norwegian, and many European languages, use comma to separate units and 
fractions, and the dot to separate thousands. Sometimes quite confusing....)

                   Harald



From owner-ietf@ietf.org  Tue Feb  4 01:36:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02225;
	Tue, 4 Feb 2003 01:36:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18fwhl-0005XW-00
	for ietf-list@ran.ietf.org; Tue, 04 Feb 2003 01:37:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18fweG-0005Sc-00
	for ietf@ran.ietf.org; Tue, 04 Feb 2003 01:33:36 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02039;
	Tue, 4 Feb 2003 01:28:56 -0500 (EST)
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h146Uvkn018709;
	Tue, 4 Feb 2003 07:30:57 +0100 (MET)
Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 4 Feb 2003 07:32:31 +0100
Received: from cisco.com ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 4 Feb 2003 07:32:31 +0100
Date: Tue, 4 Feb 2003 07:32:43 +0100
Subject: Fwd: Public Review Issues update
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: iab@ietf.org, iesg@ietf.org
To: ietf@ietf.org
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Content-Transfer-Encoding: 7bit
Message-Id: <77391D62-380A-11D7-87FC-0003934B2128@cisco.com>
X-Mailer: Apple Mail (2.551)
X-OriginalArrivalTime: 04 Feb 2003 06:32:31.0156 (UTC) FILETIME=[31CBF740:01C2CC17]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The following has been received from the Unicode Consortium.

Comments either to Unicode Consortium according to specified 
instructions, or to myself as liason from IETF to Unicode Consortium.

     Regards, Patrik
     Liason from IETF to Unicode Consortium

Begin forwarded message:

> From: Rick McGowan <rick@unicode.org>
> Date: tis feb 4, 2003  02:15:32 Europe/Stockholm
> To: notification@unicode.org
> Subject: Public Review Issues update
>
> Please note that the Issues for Public Review have been updated with a 
> new
> review item regarding tailoring of normalization. Please see issue 
> number
> 7 on this page:
>
> 	http://www.unicode.org/review/
>
> Instructions for discussion and submision of formal comments are 
> provided
> on that page. The closing date for review comments is February 28, 2003
> (2003-02-28).
>
> Also, the review period for issues 1, 4, 5, and 6 is quickly 
> approaching,
> and these items are expected to be discussed at the next UTC meeting 
> March
> 4-7 2003.
>
> Regards,
> 	Rick McGowan
> 	Unicode, Inc.
>




From owner-ietf@ietf.org  Tue Feb  4 11:28:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27443;
	Tue, 4 Feb 2003 11:28:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18g5sg-0002IE-00
	for ietf-list@ran.ietf.org; Tue, 04 Feb 2003 11:25:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18g5rv-0002Fk-00
	for ietf@ran.ietf.org; Tue, 04 Feb 2003 11:24:19 -0500
Received: from mail2 (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27026
	for <ietf@ietf.org>; Tue, 4 Feb 2003 11:19:29 -0500 (EST)
Received: from ran.ietf.org([132.151.6.60]) by www.heinfo.net(AIMC 2.9.5.2)
	with SMTP id jm03e3a23f8; Fri, 31 Jan 2003 12:56:10 +0800
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eSts-0002DU-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 23:35:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eStL-0002An-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 23:35:03 -0500
Received: from iagu.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18415
	for <ietf@ietf.org>; Thu, 30 Jan 2003 23:31:18 -0500 (EST)
Received: from [203.32.153.90] (andrewr@localhost.iagu.net [127.0.0.1])
	by iagu.net (8.12.3/8.12.4) with ESMTP id h0V4YnCt026280;
	Fri, 31 Jan 2003 15:04:49 +1030 (CST)
	(envelope-from andrewr@iagu.net)
Mime-Version: 1.0
X-Sender: andrewr@127.0.0.1
Message-Id: <p05200f02ba5fa9a1092d@[203.32.153.90]>
In-Reply-To: <200301310321.h0V3L46g027231@turing-police.cc.vt.edu>
References: <200301282312.SAA11118@ietf.org>
 <7856.1043838807@munnari.OZ.AU>           
 <p05200f00ba5f55d5653e@[203.32.153.90]>
 <200301310321.h0V3L46g027231@turing-police.cc.vt.edu>
Date: Fri, 31 Jan 2003 15:05:17 +1030
To: Valdis.Kletnieks@vt.edu
From: Andrew Rutherford <andrewr@iagu.net>
Subject: Re: WG Review: Enhancements to Internet email to support diverse
 service environments (lemonade)
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:21 PM -0500 30/1/03, Valdis.Kletnieks@vt.edu wrote:

>Life sucks if the mail server 421's you when you don't have local storage.....

Agreed. :-) Hopefully the gateway in question has:

(1) Got the SMTP conversation up to DATA / 354 before giving off the
"beep" that everyone expects before leaving a message - preferably even
before playing the initial greeting, so 421's from load, etc, can be
caught as early as possible.

(2) Some form of "System error" message it can then play at the person
trying to leave the message.





From owner-ietf@ietf.org  Thu Feb  6 10:49:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23146;
	Thu, 6 Feb 2003 10:49:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18goAa-0006bh-00
	for ietf-list@ran.ietf.org; Thu, 06 Feb 2003 10:42:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ghaG-0006Wc-00
	for ietf@ran.ietf.org; Thu, 06 Feb 2003 03:40:36 -0500
Received: from prv-mail25.provo.novell.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08473
	for <ietf@ietf.org>; Thu, 6 Feb 2003 03:35:21 -0500 (EST)
Received: from INET-PRV1-MTA by prv-mail25.provo.novell.com
	with Novell_GroupWise; Thu, 06 Feb 2003 01:38:58 -0700
Message-Id: <se41bcb2.059@prv-mail25.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 6.5.0 
Date: Thu, 06 Feb 2003 01:38:38 -0700
From: "Nitin Khurana" <nkhurana@novell.com>
To: <ietf@ietf.org>
Cc: "Milind R Parvatikar" <RPmilind@novell.com>
Subject: Comments about 'Finding Remote DA's  and SA's in SLP via DNS
	SRV
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
    The proposed mechanism for finding remote DA's using DNS SRV is an
excellent mechanism for overcoming the network traffic generated during
the multicast SA/DA discovery and to make the SLP protocol scale to the
internet. However the following things may be considered:
1. The administrator overhead of putting SRV records in the DNS
database needs to be considered. To reduce the administrator overhead
another feature which can be included is the dynamic updates (RFC 2136),
whenever the DA comes up it sends an update packet to the DNS Server
which adds the SRV record. 
2. Also if the DA/SA/GDA goes down the corresponding SRV record in the
dns repository has to be deleted. It is near impossible for an
administrator to monitor this and add/delete the corresponding SRV
records from DNS everytime the DA/SA comes up or goes down, so the
dynamic updates done by the DA/SA would solve this problem.

Regards,
Nitin Khurana.





From owner-ietf@ietf.org  Sun Feb  9 01:31:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10867;
	Sun, 9 Feb 2003 01:31:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18hksC-0007qC-00
	for ietf-list@ran.ietf.org; Sun, 09 Feb 2003 01:23:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18hkry-0007pr-00
	for ietf@ran.ietf.org; Sun, 09 Feb 2003 01:23:14 -0500
Received: from ohsmtp02.ogw.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10624
	for <ietf@ietf.org>; Sun, 9 Feb 2003 01:17:19 -0500 (EST)
Received: from Fokk (dhcp065-025-033-010.neo.rr.com [65.25.33.10])
	by ohsmtp02.ogw.rr.com (8.12.5/8.12.2) with SMTP id h196KNHk002859
	for <ietf@ietf.org>; Sun, 9 Feb 2003 01:20:26 -0500 (EST)
Date: Sun, 9 Feb 2003 01:20:23 -0500 (EST)
Message-Id: <200302090620.h196KNHk002859@ohsmtp02.ogw.rr.com>
From: anthony <anthony@atkielski.com>
To: ietf@ietf.org
Subject: Fw:eager to see you
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=Q887874336f35K65zx42L6ROh5788dS
Sender: owner-ietf@ietf.org
Precedence: bulk

--Q887874336f35K65zx42L6ROh5788dS
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

src.pif is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--Q887874336f35K65zx42L6ROh5788dS
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:F5kS09a628g8414u height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--Q887874336f35K65zx42L6ROh5788dS
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

src.pif is removed from here because it is of type executable

---------------------------------------------------------
--Q887874336f35K65zx42L6ROh5788dS

Content-Type: application/octet-stream;
	name=main_13[1].jpg
Content-Transfer-Encoding: base64
Content-ID: <F5kS09a628g8414u>

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAALQAA/+4ADkFkb2JlAGTAAAAA
Af/bAIQACgcHBwgHCggICg4JCAkOEQ0KCg0RFBAQERAQFBMPERAQEQ8TExcXGRcXEx4eICAe
HiwrKyssMTExMTExMTExMQELCQkLDAsNCwsNEQ4ODhEUDg4ODhQXEBAREBAXHhYTExMTFh4b
HRkZGR0bISEeHiEhKSkoKSkxMTExMTExMTEx/8AAEQgAPgFpAwEiAAIRAQMRAf/EAJEAAAID
AQEBAAAAAAAAAAAAAAQFAgMGAQAHAQEBAQAAAAAAAAAAAAAAAAAAAQIQAAIBAwIEAwMIBgYJ
BQEAAAECAxEEBQASITETBkFRIjJCFGFxUmKiI5MWgZGhYzQVscGSMzYHckODo9MkVGQm0YJT
hDdHEQEBAQACAwADAAAAAAAAAAAAARExQSECEuEyQv/aAAwDAQACEQMRAD8AtOaynxXxnxj/
ABIXYJOqa7fo+VNDS3tzLdfFyTF7ncG6rSEmq0pz8qa6ElYhVV2Y8gNpqfk1ySKaNtrpIjeK
sFB/bqNrJcvkZVlV7lmWd1klG8+plptblzG0a9JnMtJNDO97I0tvXpMZT6aihp8456oEcrGi
h2POgCk690ZmJASQleYotR8+iL5M9l5Q4kvHfqRmF6vWqNzXloZL26jtZLNJSttMQ0kQc0Yr
QivDwpqJVx4N9nXNrfW+zoDm7izTEsb16llYnf7y+yfZ8NVnN5VpIpTdv1IGd4m3kFWkJLkU
HvV46F2v9b7OpLDM/FUkYcqgA8fLQEnPZgzpcG9kM8SlEk6hqFbiRy4/p1CTMZSS3S2kvJGg
jIZEMjUBU1X9Xh5aoaORTRg6kcwQoOubW+t9nQGt3BmWZWa9dmjfqoS5NH2lN3L6J0Gt1Ol1
8WstLkP1BJvNd5Nd2urDKwJVXYDnQA/0ajtb632dAbN3Dmp0ZJb13V0aNgX5o/tL7PjTVD5T
IOluhuW22f8ADUcjp0oPSQK+GqdrfW+zr21vrfZ0Fl7kLy/kEl5cNO6iil3JoPIasOXyZs/g
TdyfCU29LqtTb9H5vk0Ptb632de2t9b7OgM/n+ZMaxG9kMabCqmQkAxEMnMeBA10dw5oMGF6
4ZWZwd/Jm9o8vGugtrfW+zrqxyMaKHYnwAUnQWjKZBbM2IunFoa/c9RtvHiRTyr4a7ZZXI2C
stndPArkMwSQipXlqowTqKskgHmQKajtb632dAYufzC+zeMADIabvGU75PD3idRGayotfg/i
3+G2dLpGQldnly0Ltf632de2t9b7OgutcnfWcbRWtwYo3ZXZVfgWQhlPEeBGrJMzlJTGXu3J
hdpYiJCCruSzMCAOdTocRTFSwVyo5sAtOHy64Fbyb7OgLbN5Vp2uGu3aZ4zCzmQn7smpWlKU
rquLK5GG0ayiunS1eu6ISNtoeY+Y+OqxBORuCSFfMAa5tb632dB25u7i7dXuZeq6II1ZnNQq
8hy1Vw8x/bOrNr/W+zqaRyOwUbzX/R0EYUDHcStB9c6v9Pmv4h1eEdQFG/h/oa9tf6/2NStS
KPT5r+Idc9Pmv4h0Rtf6/wBjXtsn7z7Ggo9Pmv4h170+a/iHV+2T959jXtsn1/saCj0+a/iH
XfSoLErQfvDohY5WNAJCf/Zqqfq7tpEiqvgQoPz6oFJDMSSOP7w65QeY/tnRDRTKKssgB5Eh
f69R2v8AX+xoir0+Y/EOvenzH4h1cFf6/wBnXdsn1/s6CkbfNfxDqQ2+a/iHV8cM8jhI0ldz
yVQpP6hqUlvcwttmjljbntYKp/boKBt81/EOpDb5r+IdTAk+v9jUgJPr/Y1BAFfpL+KdSqv0
l/FbUwJP3n2Nd9f1/saK2mHt7XHvn7u3hQSW0sgj9NKKqdXZw8Knw0D3LMmS7Rs8rPGgumMb
AhSQN1VYCprQ/PplbCsHcyr6maabgDU16CimlGWUp/l7ZI42n7rgSR4sfH5NaYCdhAfzs0AH
3D+6R4p4nWlwdpdRdw5qeWFo4ZmToyFSA4G6u0+Os32FT+cniP4d/eJPNPDWow+XvLzO5exm
Km3sWQQgCh9Va7vPUheWXxvbtjeQ3+Wykxgs4ZpV9C+qiHixJD+fIDR0HbFljc9jZo599ncb
mhDqN29QCqkigowPlrsH+CMtTmJbmvH95phkuE3bA/fL4/utU1ne/obSPLxGNlM0kf3sWyuz
bTaeH0qnTrsh5Ie272WFOpLHNK0cYU+plijIXaOPE6z3fS/+TOTQVhj5sR4HWg7Okkh7ZyEs
PGWKWZowDv8AUsMZA/XqHTndrrc9qQX1/brb35MZRGHqVmPqXj6vZqSNDxdkYeNrezvbmQZG
6RmRY1GyqAFuaNyr4sK6uyyS5fspL3KQrFkUoUJBQqxlEQ58RvWnDTCytLHCZLH423h6s95H
KZbyVi0lI1rRa1puJ8NUC9r4/wCBgzVhI6jpSbDLtoNpjqHIqfA10lyfauOixVpf4y4a4Fy8
abpF4N1PSGUUVl4+B1pLOrXXcwHE7wAP/rjS9eHZ+E40/wCYtPH97oIDsfCCVbCS7k/mTxGU
AKuzaDtLbdvn9bS3F9pWrx31zlZ+la2EjxOYk9RMftPxDcOPlrW3+Qu0zkNjZWlvLcvbNN15
3MZCh9pQFI5Dz0jxV7mLC7y11eW6S4c3MvxmyQP0nFA7IrhSy0pUU1DSLuft6HDTwGGTq210
rGIsgLApSoO2lfaGgcPFG+XsFdFZGuYQymM0ILrUGvDTTu/A2WNube8sTstr4Mwi3EBWFDVP
kIbl4aAwtP5xj+I/ioffJ99fDRZwn3RFDH3DexRRpHGrLtVY+A9C+Wi+ylA7it+A9mT3CPcb
x0N3TT8zX3ED1r7xHuLozsyn5ht6EV2ycnJ9xvA6HTcQXl7cZi+sLizpjokQw3LKdshZVLL6
vS3M8vLWMxfbWNyEuUvppujirKeZIzEorsjJfcGIbgEp4a1FrlZ7rubKYS4SOSyghjdARxo6
R7lbwIO86B7e6ONwvcAjiEsNleXm2BjUMsUa0Rqg8wtNVCPM9qW9uthPjZutbZKSOKIyrxDS
jdG1QF4EfJpkOyMKZmx63cpySRCU+hdgUkoGpt8/Ddr2ZGTy2Mw0csNvZWd5c2xhMErmRA8b
7RsMSKKKfBtO8YlnYZZ8TaW4RUtlnkuGYtK5L7FVieNBz0NJcVGYOy8vE1N8LXKNQGlVVR/T
rDIFZa0H9g631qCe1u4B53F746x+Isjc3dtAdpEsqKQJDyLCvDUWPqGOSO2s7LGOo3taksOV
emI0fh88msJge14sochHLL0pbGTpAbOBPqHqr8q63ktsjZq3u/iVR44JIvheG5hIVcsPVX/V
+WluJtfhsp3Co4CR45V4/wDyRs5/aTqoUv2Vh/hYLqO/UW5YdedtmxgfT934AlqDiTqm+7Tt
7bLWljayVW9DUaVAzL0xuc1XaOXLVxFP8vrQV9+PjX9/56Ydx2C5DP4m1d2jjZJ2kKMVYqoV
qLTz5aiy0LL2piZEuorKZjeWQHVV0BTcV3gcFXmPlOiPh8f+SQWkUQ9EOZdn+s379lP9P06Y
Y6W3STJ4+2gWGKw2DcGLM7OhZmcnjXw1nz6v8s/P5a+V3zrpibRUXaWKiFtbXs7C/uwxjRFA
UlF3OKFW9kHzGhcf2pFcX1/ZzyhWsmjAZY/aEgZgeJ8gOWtFlr+aDI421trWG4ubvr9KSZig
j6aKzUZY5D6hoXANctn86bpY0n/5TesTl0H3bUoWVDy+TTF2s7/I7b8t/wA53jf9Dp8P73pf
Py0xv+zra0tp7kS744YXcDYKlwPTy8PPUJI5Yf8ALgpKpjkWlVckEVuuHP5NR/zJllC42JXK
pIZiy7ioJXpgfPTcdDaW9tun8+s1QL7bVIjK+43Cuvd7MPzC60HCKM+yWPLVXaoAzdlxBO5u
Ack+w3horvKyu5M/JOkEjwiFCZQG2igNeIBHDQvJxmMe14uGtLqcCK4JVSsdCpEW4c2PMimg
Y+z7T4m/SSciGxCMrCMVIZOo1eP9GjO6Ln4WDt+4qAIZ43Y1pwCrX9mmPcriywuWugaNOixg
nh7YWEU/taJpJZdqYkWVnNkZ2Sa/2CBY1AG5xuVT6X8Pm0jzWKGLyD2lVkUAPG/TPFW86Hnr
aT372mLwgit4rqa6MEUPVbaqO0dQ+4I58PAayfdj3pzg+NWGKUQJ6YpmZaVbxZENf0aLL5Pe
1hHY9u5DJRopuIxK1dpWoij3qp8eehchncfl+0xLdywDKD1LCPaDLJs4ITu4porBjqdnZONP
W5S5XarFiSYhw0kTtezXtYZiZ5Eudu7ps1E/vemvhXiNE7N7btLFItrBezsL69VmiWNQEqi7
291vZB8SK6os+0Yp7rIWssqq9kyhWEdAwdS6lqnyppzaWlng77F2EUXVub8TCW6kYs46Ue9t
m6tAxpy8NWWJJzPcI8vh6cf+3GhtLH7RxHw0Fyl6ggJHWnYJsYH0+jlQlqDiTo78j4f6U360
/wCHpU//AOe2vGnrj41/7jz1t+Py/s08G18wxmXzWMlmuo6zG5O6dJQpVm57vSVIPHw0Nmu4
cxmykNyght4m3CKIUBbkGbezVpplLbIjvEyIHjJVh0G5jgfHSye3jRz6VH+yYaNfKzE5K6xF
x8TDH1HKFKSAFeNDX0sp8PPVtp3HlbK+vL6O3iaW+KmRWUlRtrTbSQHx8ToJoaU3IBXlWJuO
uCMeCjjyHSbQsF4ruXK4sTiOJZYbh2keGQDaGbmV2sD+uuoXvcWXyV/b3soETWTb7eOMAIpq
Ca7mJNaceOqNq8iiH/ZNpzB2neyWcl3IkVukalwkiEMQoryGmphfl8ze5uaBrmEQtbhgDFSh
3EVrvZvLRFh3DlMLaNb2kUcqvIZCZlqalVXhslXh6dew/b82VlcQ9OOOKm+R4yOfIAV48tEZ
ftmfGRJOXiuIHYJuSM1DHlUVPDQ8cFeW7jz+ZiFvPthgqGMUI2gkcql2ZuHz6OfvfPp0C1tA
0sAKtKyVZwRQ1o4pXgTtpx00i7HuWhDPLbxzMKiIxk/oLbv6tZ65tDBPJbyookiYq46RPEfM
dDIsg7vzkMt7NHDEsl+waRtreghBGDH95w5V411Vle6MzlrWK0mjSFImVy0Q2lmXkTViB+jT
XF9oT5C2F00kVvC5ITdGSxoaVpuWgroe47XvIMnFjtsTyzjdFIEOwqK1JPhSmhkd/PvcCQCI
wQtMF2/EFTu+cgPtr+jQWH7lzGL65VRcpdOZJUmAILt7T+krxPjp1edj3MFs88csM7RAs8Yj
INAKnb6jU01Viu0J7+2W6eSK3hcnZujJY0NK03CnHQ8EWUzGUzV2k136ViBEUUYARQedNxJq
ac9E4dJBlrCu+nxMPPZ9NfLR99gv5ZOIZhG5YbkZYmII5eeicbgJL6KSeCSOBoDUExMrVA3A
r6hpq54K+5Y5G7lvtoY+teW36C+evY6a+xtyl7Cm6SMMAsgUqdwK8drKfHz0wtcDNc2M2XeZ
H27iwkjZnOz5S1ddu8VHb2MN4ZYJBPtpGsRLDcpfiN3yahJOAcGfysOWusssEZubpFR0Knpg
KEUFR1N3ufS1zH9wZewubu5iiVlvZGllgYVTexJJX17hz89cMCDmiior/cty0fZYI3lnPdq0
SJb7tytEwJ2ru89Nq/MLr/uLNZK5gmdegLRxJDHGBtDj3juLV5aOfvbOrOJUtYA2zY1UJ3UN
QSRIG4caCvidAiCMcdiivEfcNq+zxpvblLeJE3v4tEwAA5kmumnzFEWfyyWN3ZCCPpXzyPI2
07gZfaCfeAfNUa5jLi5sJI7lEMjxVKq+0rWhHHaVPj560UnZbhG6U8EkyDjH0iPmFd5/o1nu
mgJXaoI4EdFuH7dLpMRmzWWmzkeZ6SC5gXaiAfd0oy8Rvr7x8dF/nDOCeeX4WAPcIiSelqUT
dQj73n6tC9KP6K/gtrpt1pu6Yp59B6aafMQObyhw8eJ6KfDxFSr0PU9L9TiepTn8miLnuXNX
N/a3xiSKaz3bAi+lg/Bg4Z28B4aLTAlsU2T3RCNa1QxNu4Ns89SnwSw/ChZbeR7x1RAsZ9Je
lN1Cac9PJkUv3pnOpKUtYFWYAMNh5gbd1RICSR5+WhbHP5WxxT41YVlgkV1DOPUokruoQwHj
5aIyWJbHXCwTiFndA46cbMKEkfJx9OhejGfcX8Fv/XTT5gu27zz1tapA0Ec7RrtWaRfXQCg3
bXAJ0PjM9mbK6uL0L8RJd0MyyAUJFdpG1lpTRGNxIyFyLdOnGSC25oWA4fp1VkraOxuZLP7t
5I6BmWFqcQDw4/LpqZFOR7qzd/ZTY+4jjKTsC0irR1owcKvr28KU5aqy+cyWbkt/i4Ui+G37
OiKV37a7t7v9HVfQQAHYKHkei1DrphUGhRQR5xNqmLbO7ubG4ju4VLyQklVcKVNQRx2lT4+e
jLjvrOzRyQPa24SVWQlVetGG3hWU6Gto1UMxjWpptYwt+zXWihYktChpzIhcf0EaFijKZvJZ
aC3triJI47b2DGKMfTt9W52H7NW5fuTMZOzGPnijWGqlnRSHO3z3SMP2a58PankAv+yamumx
joCNvHlWBwD+njoZBFl3dmsdZx2ohjuEhFImlHqUDgBVHXgNK5bu/wAjePeXZZpZPohQABwC
gHwGijYs3sor08om/r1EWrDlED80LHQwRYZvKYhna1HUjkoXhlClSR4jaVIP6dU5juXM5mNb
eVBBbghjHEPaI5bi7NXUGiA4MgHyGFhqIijHur+E2hhie9M6iwDoQvLAKdZ0qzClCD6+FfGl
NUw92ZqO5vblbeEvkNnVBVqL006Y2fe+XnXQpiQ+6v4La90o/oL+C2h8pHOZQ4ePEdFPh4ip
V6Hqel+oKnqU5/Jpr+e89/0lv/Zb/jaU9KP6K/gtr3Sj+iv4LaGNx1RPZ5yKgMltLLt4+BQO
OI4jjXV9yts+dsLQqD0YJZwPM1SNSR4046BwbSNmc+JUZIGcbySpAoHA9knmvHUg0356IdG2
fBUjNRTbWu7z9qo1WR2QiuJ8Zk1v44xGgkNqUPHYqVVm8mroOPIY7Hdt4/I3aFgiRGMKAWLs
hA4mngTpdeR4yMZpr2WSe6eSdrdVFwAg2elPZVOfzjVWfp+RcbWtKwV5V9htQZeKQSLWo/TK
2tvhMhd3vb2Te5l6rRLKsZqOAEVeYA1j7URiMcZD/Y/r1rcD/h3Kc/Zl57a/3X1dI17cKezX
LYTJGvEA+8T7h89dhcjsewatT1YeNT/1HnqPZA3YnIpISiHnIdppVDXgvHhq26VIOzbNLdze
RrLDtlUbN33272ZNvjw1WbyPvifzfiwDQfDz8K/IfDWWzzKe4r5SRwZechX3F8BrY3UUDdyW
ErT7J1hlCW+0kuCOJ3AUFNZ67hx0uZyj3lxLbXCyAQxKAwYBFoahG5/PqVfXkTlSR2dZ7TT7
yHiGP0vpc9OLtqdy45fAwXHj5bPDS65jin7UtFuZvhF3x/eOu/k5oKR156OvWcd041dhK9Ce
r1WnHb8teFB+vRO1OHYnJdwAn2ZVpxJ9xv1aX3srHsuxcNQs0PHcfpHx56aWEcMV1nJIZviZ
XcM8IUqUYI1F3PQGvz6XiOKfs2wW4m+EXdHR2UvWjmnCOvPQV97ybLuwFQAyye+U8U8tG9pl
XtLsbhtLAEhy9Kr5nS/vgv8AH2ChWACP6ht41K8PV5aP7X3fAXu7dz97b9E/R07X+Vj2ttY9
q3sVrci6iWKVhMGB4kcRuUnloe8WM4bt0MopNcWSvxpUNGaivjXQeE/wHecT7NxxNK8tE5Fp
EwHbjRoZJFuLErGCoLMIzRatQcdEOGu93cC45o0KLZ/EK5HrBMnTp5UpoHFXCLbZ6QqHSC6u
aoWJBCj2fk0Yj2jdwrWORL82RJ3FdgiEo4ekt6ixP6tLMZ/Bdy8/4q7py+ieWgh3BeJc9s2N
8yLGZWiYKGKhd6NUBh4aG7SdWynAqfunPCQv4r4HXcx/grGUrzg5Ur7Dfo1HtMyDJJwdgYnD
V6dAOHHhx56dtT9aNwTMe680CeA2ilSeR8tcR1HbWUkIFUnuRWvlJ56LxMFqncGVliuutM5X
qQbGUx+dWIAP6NCWSpN2xkluZDaI89z1HI3lKvx4JWtPk0Z/CWeuLW2t8RLcIWiLqXVTxb0A
08N3HwOm9m9zeGb4i26Fg6osEUgCynh696qTtHloHJiFbnAAkPCJqKxAAP3fpND8tNF2qSjO
37vISrRQCKM14AbqkVWnPyOhSPqD8jXDKfZLAHcTymp7WjMjOLWTt+REWskyRmvDhIgjJ4c6
bq6Ajr+Q7nn7UnlX+/0XnK/+Oc/4mDgKfU0UxlyNO5Y8W6r05LMzKx9ovvK7fmCqdLMlIll2
3NUBXluZYgS1OUzj2ufspqWTWnemMkifdMYSrwgco/vauWPDxPjXhoTvwyCws1hBa2NzKZXS
gpJVqKQfnf8AVok6U9qXCSZeNEoR03qRIz14eR04w6pL3Dn1cBgGtxQ8eaPXny0i7O3fzaP2
6dN/a205fJx0+wn+I+4OftW3l9B9Ivtyg2chbtVM21rGREQ0cG70qRL0AQ239PLVPdc9na5T
ETXMZkjLS71Q+ptvT2ALUBvU2l3/APMvH9lf4vTvNdP8x4DqU27rmlaU3bE2c/rU1UG2hur4
XIu7f4exkCrbROAJabfvC4UkL6vZ46T21+LPs6C7WNJOoQrq5JVupLsNTz5aa2CSjO5Z3kLK
62vSjO70qEflVQtC1eROkOOmt/yVAMjby/Doy7WRk9Z61Up6qgbuBqNA2yUUD9w4qB0BBSd9
taAlACKgc9GzR3E6X0N5HH8IRS2Kn1EbfUW8iDy0DkSR3Th6AkGK5BpSg9I48dA3UeNjyWVk
yEskzPtNvCouBspHxFVVU4n5SNQF4S4p2/bXGLRLh1IN1Huq5pXqKpJ9ryr4ayuQytrd5GWW
CEwK1A0UjmNg4FG9Knhy047VhtDBbPiLh1ug0ZyccgcxslCGA9G3d4rx0H3MY/5/MIlIoiCQ
ps4vTnx8aU0WcgPiEpSq08jO1NceOJwWjZARzXrN+zhrqh6eoyj8PVi9SvoM27w/u9GgdV+k
v4za9VfpL+M2jZKkUferea9I8fl264iwj2nmJ+aP+vUUINp95fxm1LZ8q/jNpnHt9zq/7rVn
3n73/daaY//Z
--Q887874336f35K65zx42L6ROh5788dS--



From owner-ietf@ietf.org  Sun Feb  9 06:37:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26211;
	Sun, 9 Feb 2003 06:37:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18hpjA-0003cw-00
	for ietf-list@ran.ietf.org; Sun, 09 Feb 2003 06:34:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18hpj6-0003cb-00
	for ietf@ran.ietf.org; Sun, 09 Feb 2003 06:34:24 -0500
Received: from relay-4m.club-internet.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26063
	for <ietf@ietf.org>; Sun, 9 Feb 2003 06:28:27 -0500 (EST)
Received: from mine.club-internet.fr (f09m-2-170.d1.club-internet.fr [213.44.217.170])
	by relay-4m.club-internet.fr (Postfix) with ESMTP id E2618E2BA
	for <ietf@ietf.org>; Sun,  9 Feb 2003 12:32:05 +0100 (CET)
Message-Id: <5.2.0.9.0.20030209093137.02d4c670@pop.online.fr>
X-Sender: jefsey@mail.club-internet.fr
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sun, 09 Feb 2003 09:51:59 +0100
To: ietf@ietf.org
From: "J-F C. (Jefsey)  Morfin" <jefsey@club-internet.fr>
Subject: user classes and host groups
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

In several debates - at least IDNs, OPES, RID-DoS - the notion of closed 
user groups - or better the notion of user classes and of groups of 
targeted hosts (permitting an independent user/host on the fly management 
of CUG equivalents) - could be of use. The IETF database is not of real 
help to understand where this is discussed? Thank you for your help. jfc




From owner-ietf@ietf.org  Mon Feb 10 04:39:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01897;
	Mon, 10 Feb 2003 04:39:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iAEo-0001cL-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 04:28:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iAEH-0001bk-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 04:27:57 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA01356;
	Mon, 10 Feb 2003 04:21:44 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e479562; Mon, 10 Feb 2003 09:25:23 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jmd33e3a7e6b; Fri, 31 Jan 2003 06:23:32 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eGqX-00070d-00
	for ietf-list@ran.ietf.org; Thu, 30 Jan 2003 10:43:21 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eGjG-0006KR-00
	for ietf@ran.ietf.org; Thu, 30 Jan 2003 10:35:50 -0500
Received: from klutz.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01049;
	Thu, 30 Jan 2003 10:27:35 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id B520913FB9; Thu, 30 Jan 2003 10:31:08 -0500 (EST)
Received: from klutz.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 01085-09; Thu, 30 Jan 2003 10:31:08 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id 1A930140A7; Thu, 30 Jan 2003 10:31:08 -0500 (EST)
Date: Thu, 30 Jan 2003 10:31:07 -0500
From: Keith Moore <moore@cs.utk.edu>
To: RJ Atkinson <rja@extremenetworks.com>
Cc: moore@cs.utk.edu, narten@us.ibm.com, braden@isi.edu, ietf@ietf.org,
        kireeti@juniper.net, iesg@ietf.org
Subject: Re: "IETF consensus"  in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ]
Message-Id: <20030130103107.305bb5fd.moore@cs.utk.edu>
In-Reply-To: <1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
References: <200301300120.h0U1KQo02850@cichlid.adsl.duke.edu>
	<1261B871-3460-11D7-AE59-00039357A82A@extremenetworks.com>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: 50b238bb42e937701f7caf8b786e4cff35873c40
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I don't know what can be done a this point to change the terminology
> > in 2434. It's been in use for some 4 years now...
> 
> It would seem quite simple for you to take the text of RFC-2434,
> edit the text appropriately to pick a more clear and accurate
> term, then run it past the community for BCP.

well, the phrase "IETF Consensus" would still be embedded in several 
other documents.  are you claiming that it's simple to update these
also?
 




From owner-ietf@ietf.org  Mon Feb 10 05:08:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02850;
	Mon, 10 Feb 2003 05:08:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iAtQ-0002JE-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 05:10:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iAt3-0002If-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 05:10:05 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02737;
	Mon, 10 Feb 2003 05:03:51 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jma3e479f41; Mon, 10 Feb 2003 10:07:31 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm7c3e3b2b47; Fri, 31 Jan 2003 21:15:50 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18eiPS-0002O6-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 16:09:14 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18eiPH-0002Mu-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 16:09:03 -0500
Received: from e33.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18907;
	Fri, 31 Jan 2003 16:05:12 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e33.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h0VL8eE0048924;
	Fri, 31 Jan 2003 16:08:40 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h0VL8cPc066686;
	Fri, 31 Jan 2003 14:08:39 -0700
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id h0VL6gt00339;
	Fri, 31 Jan 2003 16:06:43 -0500
Message-Id: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com>
To: John C Klensin <john-ietf@jck.com>
cc: Randy Bush <randy@psg.com>, RJ Atkinson <rja@extremenetworks.com>,
        Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: Message from john-ietf@jck.com
   of "Thu, 30 Jan 2003 16:39:12 EST." <30625166.1043944752@p3.JCK.COM> 
Date: Fri, 31 Jan 2003 16:06:42 -0500
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Absolutely.  Otherwise, this discussion wouldn't be worth the 
> trouble.  But, if you are going to define "IETF Consensus" as 
> "Publication as an RFC" then

Since I don't seem to be able to make this clear enough, once again, I
do not and have never intended "IETF Consensus", in the literal sense,
to be defined as "Publication as an RFC". We all know that the two are
not the same. That term was used as a shorthand way in RFC 2434 to
indicate RFC publication was required.

If I could go back in time, I would leave the defintion as it is, but
give it a different name. I probably wouldn't have tried to define
"IETF Consensus" at all, as I'm not sure how that would be done in a
way that encompasses both standards track and non-standards track
documents (or that such a definition would even be useful).

> 	- We don't need the added term to add confusion.
> 	
> 	- We open up a loophole case in which a document comes
> 	to the RFC Editor, then to the IESG.  The IESG decides
> 	it is a bad idea, and puts a disclaimer on it that says
> 	"this is a terrible idea".  The RFC Editor decides to
> 	publish it anyway.  We now have an RFC that, regardless
> 	of its other properties, clearly does not represent IESG
> 	consensus that it is a good idea.  But whatever it calls
> 	for is eligible for registration.

What this points out is that the relationship between IESG review,
IANA assignments and RFC editor independence is both complex and
subtle. Not suprisingly, it has evolved over time in a way that no
longer matches the exact words in (say) 2026. A literal intepretation
of some of these words could easily lead us into situations that we
probably don't want to be in.  I agree that it would be good to
clarify and update the written words.

Thomas	




From owner-ietf@ietf.org  Mon Feb 10 07:38:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06927;
	Mon, 10 Feb 2003 07:38:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iDCg-0008SY-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 07:38:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iDBy-0008R4-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 07:37:46 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA06717
	for <ietf@ietf.org>; Mon, 10 Feb 2003 07:31:31 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e4807b2; Mon, 10 Feb 2003 12:35:11 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm343e3b3809; Fri, 31 Jan 2003 20:29:28 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ehd3-0006cy-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 15:19:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ehcu-0006br-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 15:19:04 -0500
Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17542
	for <ietf@ietf.org>; Fri, 31 Jan 2003 15:15:14 -0500 (EST)
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0VKIh2d029128
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 31 Jan 2003 12:18:43 -0800 (PST)
Received: from [129.46.74.134] (loud.qualcomm.com [129.46.74.134])
	by crowley.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h0VKIZ5O001402;
	Fri, 31 Jan 2003 12:18:37 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a06000257ba608a451751@[129.46.74.134]>
In-Reply-To: <20259.1044014212@munnari.OZ.AU>
References: <p0600010cba5dc6d587ee@[216.43.25.67]> 
 <200301282312.SAA11118@ietf.org> <7856.1043838807@munnari.OZ.AU>
 <20259.1044014212@munnari.OZ.AU>
X-Mailer: Eudora for Mac OS X v6.0a
Date: Fri, 31 Jan 2003 12:18:26 -0800
To: Robert Elz <kre@munnari.oz.au>, Pete Resnick <presnick@qualcomm.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: WG Review: Enhancements to Internet email to support
 diverse service environments (lemonade)
Cc: ietf@ietf.org, Glenn Parsons <gparsons@nortelnetworks.com>,
        Eric Burger <eburger@snowshore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b25
Sender: owner-ietf@ietf.org
Precedence: bulk

At 6:56 PM +0700 1/31/03, Robert Elz wrote:

>  If all you really want is to formalise a (rational) method to implement
>  biff, then that's fine, but "message status information" might be much
>  more than that.   As written it suggests more like a way for servers to
>  let other servers know when messages have been delivered, read, ... (etc).

This is exactly what one proposal (SNAP) does: it allows one server 
to communicate status change events to another.
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
Quick!!  Act as if nothing has happened!




From owner-ietf@ietf.org  Mon Feb 10 09:41:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10585;
	Mon, 10 Feb 2003 09:41:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iF4p-0002Te-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 09:38:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iF3D-0002RG-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 09:36:51 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10211
	for <IETF@ietf.org>; Mon, 10 Feb 2003 09:30:35 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e47f0bb; Mon, 10 Feb 2003 14:34:13 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm483e3b27e5; Sat,  1 Feb 2003 01:33:05 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18emOD-0003xP-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 20:24:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18emNz-0003wI-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 20:23:59 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24308
	for <IETF@ietf.org>; Fri, 31 Jan 2003 20:20:07 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA08498;
	Fri, 31 Jan 2003 17:23:08 -0800
Date: Fri, 31 Jan 2003 17:02:25 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <98639233839.20030131170225@brandenburg.com>
To: "Steven M. Bellovin" <smb@research.att.com>
CC: IETF@ietf.org
Subject: Re: "Written patent policy with clear guidance"
In-Reply-To: <20030131223115.CBC797B4D@berkshire.research.att.com>
References: <20030131223115.CBC797B4D@berkshire.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Steven,


SMB> Thanks.  This case has already been mentioned on the IPR wg's mailing
SMB> list.

excellent. thanks.

alas, so many wgs, so little time...

d/
-- 
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850





From owner-ietf@ietf.org  Mon Feb 10 09:52:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10993;
	Mon, 10 Feb 2003 09:52:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iFJK-0003As-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 09:53:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iFIV-00039t-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 09:52:39 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10831
	for <ietf@ietf.org>; Mon, 10 Feb 2003 09:46:24 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18iFG0-0000fc-00
	for ietf@ietf.org; Mon, 10 Feb 2003 06:50:05 -0800
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.12)
	id 18iFFz-0009yt-00
	for ietf@ietf.org; Mon, 10 Feb 2003 09:50:03 -0500
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 10 Feb 2003 09:50:02 -0500
To: ietf@ietf.org
Subject: mail loop on this list (and other lists)
References: <20030131223115.CBC797B4D@berkshire.research.att.com>
	<98639233839.20030131170225@brandenburg.com>
Message-Id: <E18iFFz-0009yt-00@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

ALERT: mail loop in bta.net.cn over in bejing

> Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
> 	by ran.ietf.org with esmtp (Exim 4.10)
> 	id 18iF3D-0002RG-00
> 	for ietf@ran.ietf.org; Mon, 10 Feb 2003 09:36:51 -0500
> Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
> 	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10211
> 	for <IETF@ietf.org>; Mon, 10 Feb 2003 09:30:35 -0500 (EST)
> Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
> 	with SMTP id jm23e47f0bb; Mon, 10 Feb 2003 14:34:13 -0000
> Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
> 	with SMTP id jm483e3b27e5; Sat,  1 Feb 2003 01:33:05 -0000
> Received: from majordomo by ran.ietf.org with local (Exim 4.10)
> 	id 18emOD-0003xP-00
> 	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 20:24:13 -0500




From owner-ietf@ietf.org  Mon Feb 10 10:05:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11491;
	Mon, 10 Feb 2003 10:05:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iFVt-0003s9-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 10:06:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iFUR-0003q2-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 10:04:59 -0500
Received: from smtp1.extremenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11248
	for <ietf@ietf.org>; Mon, 10 Feb 2003 09:58:44 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by smtp1.extremenetworks.com (Postfix) with ESMTP id E9AB07940
	for <ietf@ietf.org>; Mon, 10 Feb 2003 07:02:24 -0800 (PST)
Date: Mon, 10 Feb 2003 10:02:24 -0500
Subject: RFC-Editor relationship
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
From: RJ Atkinson <rja@extremenetworks.com>
To: IETF <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <200301312106.h0VL6gt00339@rotala.raleigh.ibm.com>
Message-Id: <A9DF99BE-3D08-11D7-BD0E-00039357A82A@extremenetworks.com>
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Friday, Jan 31, 2003, at 16:06 America/Montreal, someone wrote:
> What this points out is that the relationship between IESG review,
> IANA assignments and RFC editor independence is both complex and
> subtle. Not suprisingly, it has evolved over time in a way that no
> longer matches the exact words in (say) 2026. A literal intepretation
> of some of these words could easily lead us into situations that we
> probably don't want to be in.  I agree that it would be good to
> clarify and update the written words.

ASIDE:

An operational bug at present is that while the RFCs clearly state
that the IAB is responsible for the RFC-Editor relationship, the
actual practice is largely that IESG (and NOT IAB) is providing
direction to the RFC-Editor (even on matters not involving the
output of IETF WGs nor involving standards-track publication).

I think that this is a significant problem that does need to be fixed.
The two most obvious forms of fix are to re-align the practice to
match the RFC language or to revise the RFC language to match the
actual practice.  Other solutions probably also exist.  I don't
claim to know what the right fix is.

This discrepancy really IS a problem and one way or another needs
to be fixed.

It is NOT just an IETF issue, so IETF can't solve it unilaterally.
IRTF, IAB, and other ISoc-umbrella groups that do NOT report to IESG
nor report directly to the IETF also use (and need to continue to use)
the RFC-Editor to publish documents.

My personal preference would be that this bug get sorted out with
full input from the broader IETF community, IRTF community, and "other
folks who publish RFCs" community [1], rather than being worked
out behind closed doors.

Ran
rja@extremenetworks.com

[1] Those communities each overlap, but they are NOT identical in 
practice.




From owner-ietf@ietf.org  Mon Feb 10 11:46:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15189;
	Mon, 10 Feb 2003 11:46:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iH1n-0006aw-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 11:43:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iGzl-0006H9-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 11:41:25 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14741
	for <IETF@ietf.org>; Mon, 10 Feb 2003 11:35:07 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e4834b0; Mon, 10 Feb 2003 16:38:47 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm63e3b299f; Fri, 31 Jan 2003 22:18:10 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ejMT-0006hp-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 17:10:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ejLl-0006fq-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 17:09:29 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20244
	for <IETF@ietf.org>; Fri, 31 Jan 2003 17:05:38 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id OAA32376
	for <IETF@ietf.org>; Fri, 31 Jan 2003 14:08:55 -0800
Date: Fri, 31 Jan 2003 14:09:09 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/4) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <41628837320.20030131140909@brandenburg.com>
To: IETF@ietf.org
Subject: "Written patent policy with clear guidance"
In-Reply-To: <0DC042C355EBD6118C5600105A5B9AD224526D@PANTEMERGENCY>
References: <0DC042C355EBD6118C5600105A5B9AD224526D@PANTEMERGENCY>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

Norm Beamer is a partner at Fish & Neave, which specializes in
intellectual property law.  They did the patent for the Wright Brothers.

I am forwarding his note at his request. This is not intended to state a
concern that the IETF's current efforts regarding intellectual property
are inadequate -- my non-expert guess is that we currently have pretty
good policies and communicate them well.

However it seems worthwhile to take note of a case and a warning that an
expert thinks is relevant to us.

d/
----- 
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850

 
==============Forwarded message===============
From: Beamer, Norman H. <NBeamer@fishneave.com>
To: "Dave Crocker (E-mail)" <dcrocker@brandenburg.com>
Date: Friday, January 31, 2003, 12:25:11 PM


I suggest you pass this on to IETF colleagues   

On Wednesday, the Court of Appeals of the Federal Circuit ruled that
Rambus did not commit fraud when it was filing patents while Rambus
employees where on a standards committee for high speed memory chips.
Rmabus will be seeking $840 million in royalties from companies such
as Infineon, Hynix (which last I heard had no money) and Micron 
(Rambus collects a 3% royalty for its chip, and this chip market is
a $28 billion industry, resulting in the 840 figure). On this news,
Rambus stock rose 57%, or 4.25, to 11.69 dollars a share.

To me there is a blunt message in the decision: that it is time that
all engineering standards committees mature in their handling of patent
issues.  The stakes are ever increasing with these standards, and
everyone knows that everyone is playing patent games.  Any committee
with less than clear and explicit rules about disclosure for patent
activities by committee members should not whine later on.  In the eyes
of the CAFC, the committee that Rambus employees was on didn't clearly
define the rules, so that Rambus' actions were not sanctionable.  For
example, in the ruling, we see language such as:

    "In this case there is a staggering lack of defining details
    in the ... patent policy" ..... "When competitors participate
    in an open standards committee, their work necessitates a
    written patent policy with clear guidance on the committee's
    intellectual property position."

===========End of original message text===========





From owner-ietf@ietf.org  Mon Feb 10 13:07:09 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18547;
	Mon, 10 Feb 2003 13:07:09 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iIK6-0006K3-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 13:06:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iIJL-0006IG-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 13:05:44 -0500
Received: from btmail.net.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA18255
	for <IETF@ietf.org>; Mon, 10 Feb 2003 12:59:25 -0500 (EST)
Received: from btmail.net.cn([202.106.196.73]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm243e483736; Mon, 10 Feb 2003 18:03:06 -0000
Received: from ran.ietf.org([132.151.6.60]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm403e3b3d0e; Fri, 31 Jan 2003 22:37:23 -0000
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ejhl-0007T4-00
	for ietf-list@ran.ietf.org; Fri, 31 Jan 2003 17:32:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ejh9-0007Rv-00
	for ietf@ran.ietf.org; Fri, 31 Jan 2003 17:31:35 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20664
	for <IETF@ietf.org>; Fri, 31 Jan 2003 17:27:43 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 41BB94CE24; Fri, 31 Jan 2003 17:31:17 -0500 (EST)
Received: from berkshire.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id RAA18467;
	Fri, 31 Jan 2003 17:31:16 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id CBC797B4D; Fri, 31 Jan 2003 17:31:15 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: IETF@ietf.org
Subject: Re: "Written patent policy with clear guidance" 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 31 Jan 2003 17:31:15 -0500
Message-Id: <20030131223115.CBC797B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <41628837320.20030131140909@brandenburg.com>, Dave Crocker writes:
>Folks,
>
>Norm Beamer is a partner at Fish & Neave, which specializes in
>intellectual property law.  They did the patent for the Wright Brothers.
>
>I am forwarding his note at his request. This is not intended to state a
>concern that the IETF's current efforts regarding intellectual property
>are inadequate -- my non-expert guess is that we currently have pretty
>good policies and communicate them well.
>
>However it seems worthwhile to take note of a case and a warning that an
>expert thinks is relevant to us.

Thanks.  This case has already been mentioned on the IPR wg's mailing 
list.  I do feel that our requirements are explicit now; we're making 
sure that they're clear enough in IPR.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)






From owner-ietf@ietf.org  Mon Feb 10 16:33:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26830;
	Mon, 10 Feb 2003 16:33:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iLWe-0008Pu-00
	for ietf-list@ran.ietf.org; Mon, 10 Feb 2003 16:31:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iLUb-0008Ml-00
	for ietf@ran.ietf.org; Mon, 10 Feb 2003 16:29:33 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26408
	for <IETF@ietf.org>; Mon, 10 Feb 2003 16:23:15 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=roam.psg.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18iLS4-000FSs-00; Mon, 10 Feb 2003 13:26:56 -0800
Received: from localhost
	([127.0.0.1] helo=roam.psg.com ident=randy)
	by roam.psg.com with esmtp (Exim 4.12)
	id 18iLS2-000AC1-00; Mon, 10 Feb 2003 16:26:54 -0500
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 10 Feb 2003 16:26:53 -0500
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: IETF@ietf.org
Subject: Re: "Written patent policy with clear guidance"
References: <0DC042C355EBD6118C5600105A5B9AD224526D@PANTEMERGENCY>
	<41628837320.20030131140909@brandenburg.com>
Message-Id: <E18iLS2-000AC1-00@roam.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Norm Beamer is a partner at Fish & Neave, which specializes in
> intellectual property law.  They did the patent for the Wright Brothers.

it might be better to use a more modern counsel.

and, as you know, it also might be better to have this on the ipr wg's
mailing list.

randy




From owner-ietf@ietf.org  Tue Feb 11 08:20:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03806;
	Tue, 11 Feb 2003 08:20:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ia9h-0007zb-00
	for ietf-list@ran.ietf.org; Tue, 11 Feb 2003 08:08:57 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iZq6-0001hx-00
	for ietf@ran.ietf.org; Tue, 11 Feb 2003 07:48:42 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01785;
	Tue, 11 Feb 2003 07:42:07 -0500 (EST)
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1BCjfn20442;
	Tue, 11 Feb 2003 19:45:42 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1BCj4b20901;
	Tue, 11 Feb 2003 19:45:04 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Thomas Narten <narten@us.ibm.com>
cc: John C Klensin <john-ietf@jck.com>, RJ Atkinson <rja@extremenetworks.com>,
        Bob Braden <braden@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>,
        "kireeti@juniper.net" <kireeti@juniper.net>,
        "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu> 
References: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 11 Feb 2003 19:45:04 +0700
Message-ID: <20899.1044967504@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Thu, 30 Jan 2003 15:45:13 -0500
    From:        Thomas Narten <narten@us.ibm.com>
    Message-ID:  <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu>

I had been avoiding reading this set of messages, because I couldn't
really see discussions of what was required to get IANA to assign a
number in some (irrelevant to me) code space could possibly be interesting.

But ...

  | In practice, "IETF Consensus" (as defined in 2434) means that
  | procedurally the IESG has to sign off on a document before IANA
  | assigns code points for it.

This is certainly true.   Unfortunately, it seems that the IESG sometimes
believes that this is all that is required (for IETF Consensus as a general
term).

That's nonsense.   Nor is "publication as a standards track RFC" or
anything similar the definition of what is "IETF Consensus" - that would
be absurd, as IETF Consensus is required for that to happen - that is,
publication as a standards track RFC is general evidence of IETF
consensus, but is not a necessary product of IETF consensus.

There can be IETF Consensus not to publish a document, just as there can
be to publish it.

IETF Consensus is the IETF's way of agreeing to some action.   The IETF
makes that decision, the IESG (currently anyway) is tasked with determining
whether or not the IETF has actually made a decision.   IETF Consensus
clearly requires a last call be made.   It does not (of itself) require
publication of anything at all - publication may be made to record the
consensus, it does not cause it, and is not required to obtain it.

kre




From owner-ietf@ietf.org  Tue Feb 11 18:51:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22204;
	Tue, 11 Feb 2003 18:51:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ikBX-0002R2-00
	for ietf-list@ran.ietf.org; Tue, 11 Feb 2003 18:51:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ikB7-0002Oi-00
	for ietf@ran.ietf.org; Tue, 11 Feb 2003 18:51:05 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22019
	for <ietf@ietf.org>; Tue, 11 Feb 2003 18:44:29 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h1BNmCb20423;
	Tue, 11 Feb 2003 15:48:12 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id XAA03474;
	Tue, 11 Feb 2003 23:48:12 GMT
Date: Tue, 11 Feb 2003 23:48:12 GMT
Message-Id: <200302112348.XAA03474@gra.isi.edu>
To: sob@harvard.edu, mankin@psg.com
Subject: Re: Protocol Action: iSCSI to Proposed Standard
Cc: ips@ece.cmu.edu, ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> 
  *> The IESG has approved publishing the following Internet-Draft
  *> as a Proposed Standard:
  *> 
  *> o iSCSI <draft-ietf-ips-iscsi-20.txt>
  *> 
  *> This document is the product of the IP Storage Working Group.
  *> 
  *> The IESG contact persons are Allison Mankin and Scott Bradner.
  *> 
  *>  
  *> Technical Summary
  *>  
  *>  The Small Computer Systems Interface (SCSI) is a family of
  *>  protocols for communicating with I/O devices, especially storage
  *>  devices. SCSI is a client-server architecture. The SCSI protocol
  *>  has been mapped over various transports, including Parallel SCSI,

Transports?

The Webster's New Collegiate Dictionary defines the noun "transport" as
"strong and often intensely pleasurable emotion".  ;-)

All the Internet documentation with which I am familiar, as well as the
OSI reference model, define a "transport layer", but I don't think you
are suggesting SCSI over IP, etc.

Can't we please resist terminology pollution?  In the IETF we call these
[data] link layers.

Bob Braden

  *>  IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are
  *>  I/O specific and have limited distance capabilities. The iSCSI
  *>  protocol defined in draft-ietf-ips-iscsi describes a means of
  *>  transporting of the SCSI packets over TCP/IP, providing for an
  *>  interoperable solution which can take advantage of existing
  *>  Internet infrastructure, Internet management facilities and
  *>  address distance limitations. Mapping over TCP ensures that the
  *>  high volume storage transfers use congestion control.
  *> 
  *>  



From owner-ietf@ietf.org  Wed Feb 12 01:16:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29928;
	Wed, 12 Feb 2003 01:16:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18iq7H-0002Tv-00
	for ietf-list@ran.ietf.org; Wed, 12 Feb 2003 01:11:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18iq5X-0002Oi-00
	for ietf@ran.ietf.org; Wed, 12 Feb 2003 01:09:43 -0500
Received: from chenqiang (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29782
	for <IETF@ietf.org>; Wed, 12 Feb 2003 01:03:03 -0500 (EST)
Received: from chenqiang ([192.168.2.19]) by chenqiang with Microsoft SMTPSVC(6.0.2600.28);
	 Wed, 12 Feb 2003 14:06:40 +0800
Message-ID: <00ad01c2d25c$e90e5510$1302a8c0@chenqiang>
From: "Chen Qiang" <chenqiang@earth9.com>
To: <IETF@ietf.org>
Subject: I want to removed
Date: Wed, 12 Feb 2003 14:06:40 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00AA_01C2D29F.F726BFA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 12 Feb 2003 06:06:40.0865 (UTC) FILETIME=[E90E5510:01C2D25C]
Sender: owner-ietf@ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00AA_01C2D29F.F726BFA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I want to removed


------=_NextPart_000_00AA_01C2D29F.F726BFA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT size=3D1>
<P>I want to removed</P></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_00AA_01C2D29F.F726BFA0--




From owner-ietf@ietf.org  Thu Feb 13 05:59:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09159;
	Thu, 13 Feb 2003 05:59:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jGwn-0007hp-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 05:50:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jGvy-0007gs-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 05:49:38 -0500
Received: from zak.ecotroph.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08948
	for <ietf@ietf.org>; Thu, 13 Feb 2003 05:42:42 -0500 (EST)
Received: from ecotroph.net ([::ffff:194.17.45.24])
  (AUTH: LOGIN anewton, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by zak.ecotroph.net with esmtp; Thu, 13 Feb 2003 05:46:25 -0500
Message-ID: <3E4B7183.1020707@ecotroph.net>
Date: Thu, 13 Feb 2003 05:20:51 -0500
From: Andrew Newton <anewton@ecotroph.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: mid-Atlantic group for Internet craft
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

After running into each other in airports and congregating in hotels
and conference centers across this planet, some of us in the
mid-Atlantic area of the US have decided that it is not only
possible but likely even useful to meet locally from time to time.
The purpose would be to swap technical opinions and engage in
networking (the social kind).

If you are interested, we have a webpage with more details:
http://ecotroph.net/magic/

-andy





From owner-ietf@ietf.org  Thu Feb 13 06:37:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09840;
	Thu, 13 Feb 2003 06:37:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jHiD-0000NZ-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 06:39:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jHhE-0000Ma-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 06:38:28 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09706
	for <ietf@ietf.org>; Thu, 13 Feb 2003 06:31:32 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18jHdz-0002cQ-00; Thu, 13 Feb 2003 11:35:07 +0000
Date: Thu, 13 Feb 2003 11:35:05 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Andrew Newton <anewton@ecotroph.net>
cc: ietf@ietf.org
Subject: Re: mid-Atlantic group for Internet craft
In-Reply-To: <3E4B7183.1020707@ecotroph.net>
Message-ID: <Pine.GSO.4.50.0302131131160.23105-100000@artemis.ee.surrey.ac.uk>
References: <3E4B7183.1020707@ecotroph.net>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.9 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18jHdz-0002cQ-00*/KyqXMjJRfM* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 13 Feb 2003, Andrew Newton wrote:

> After running into each other in airports and congregating in hotels
> and conference centers across this planet, some of us in the
> mid-Atlantic area of the US

The UK? Ireland? Airstrip One?

L.

> have decided that it is not only
> possible but likely even useful to meet locally from time to time.
> The purpose would be to swap technical opinions and engage in
> networking (the social kind).
>
> If you are interested, we have a webpage with more details:
> http://ecotroph.net/magic/

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Thu Feb 13 09:53:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13694;
	Thu, 13 Feb 2003 09:53:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jKe9-0006j2-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 09:47:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18j4Iu-0004Dk-00
	for ietf@ran.ietf.org; Wed, 12 Feb 2003 16:20:28 -0500
Received: from cygnus.equallogic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA15804
	for <ietf@ietf.org>; Wed, 12 Feb 2003 16:13:38 -0500 (EST)
Received: from cygnus.equallogic.com (localhost.localdomain [127.0.0.1])
	by cygnus.equallogic.com (8.11.6/8.11.6) with ESMTP id h1CLHM601413
	for <ietf@ietf.org>; Wed, 12 Feb 2003 16:17:22 -0500
Received: from deneb.dev.equallogic.com (deneb.dev.equallogic.com [172.16.1.99])
	by cygnus.equallogic.com (8.11.6/8.11.6) with ESMTP id h1CLHKr01392;
	Wed, 12 Feb 2003 16:17:20 -0500
Received: from PKONING.equallogic.com (localhost.localdomain [127.0.0.1])
	by deneb.dev.equallogic.com (8.11.6/8.11.6) with ESMTP id h1CLHJ426140;
	Wed, 12 Feb 2003 16:17:20 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15946.51201.426000.975061@gargle.gargle.HOWL>
Date: Wed, 12 Feb 2003 17:17:37 -0500
From: Paul Koning <pkoning@equallogic.com>
To: cbm@rose.hp.com
Cc: braden@ISI.EDU, sob@harvard.edu, mankin@psg.com, ips@ece.cmu.edu,
        ietf@ietf.org
Subject: Re: Protocol Action: iSCSI to Proposed Standard
References: <200302112348.XAA03474@gra.isi.edu>
	<00e901c2d2cd$d713e890$2cb2e40f@rose.hp.com>
X-Mailer: VM 7.07 under 21.4 (patch 10) "Military Intelligence (Windows)" XEmacs Lucid
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>>>>> "Mallikarjun" == Mallikarjun C <cbm@rose.hp.com> writes:

 >> All the Internet documentation with which I am familiar, as well
 >> as the
 Mallikarjun> I think we have a case of overlapping vocabulary from
 Mallikarjun> two different domains.

 Mallikarjun> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is
 Mallikarjun> very clearly a "SCSI transport protocol" (as opposed to
 Mallikarjun> a SCSI application layer protocol).  Parallel SCSI,
 Mallikarjun> Fibre Channel etc. are all "SCSI transports" per SCSI
 Mallikarjun> conventions.  That is all the critiqued abstract is
 Mallikarjun> trying to describe.

Agreed.

Furthermore, certainly Fibre Channel provides a transport layer in the
OSI sense.  It also provides lower layers, but it certainly is a lot
more than a data link layer.

    paul







From owner-ietf@ietf.org  Thu Feb 13 09:53:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13696;
	Thu, 13 Feb 2003 09:53:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jKe9-0006iw-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 09:47:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18j2hw-0006Zo-00
	for ietf@ran.ietf.org; Wed, 12 Feb 2003 14:38:12 -0500
Received: from palrel12.hp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12932
	for <ietf@ietf.org>; Wed, 12 Feb 2003 14:31:24 -0500 (EST)
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26])
	by palrel12.hp.com (Postfix) with ESMTP
	id 39B661C00C4F; Wed, 12 Feb 2003 11:35:08 -0800 (PST)
Received: from swathi (atl1nai177079.ssr.hp.com [15.228.177.79]) by rosemail.rose.hp.com with SMTP (8.7.1/8.7.3 SMKit7.02) id LAA10249; Wed, 12 Feb 2003 11:35:02 -0800 (PST)
Message-ID: <00e901c2d2cd$d713e890$2cb2e40f@rose.hp.com>
From: "Mallikarjun C." <cbm@rose.hp.com>
To: "Bob Braden" <braden@ISI.EDU>, <sob@harvard.edu>, <mankin@psg.com>
Cc: <ips@ece.cmu.edu>, <ietf@ietf.org>
References: <200302112348.XAA03474@gra.isi.edu>
Subject: Re: Protocol Action: iSCSI to Proposed Standard
Date: Wed, 12 Feb 2003 10:24:09 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> All the Internet documentation with which I am familiar, as well as the

I think we have a case of overlapping vocabulary from two different domains.

Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
a "SCSI transport protocol" (as opposed to a SCSI application layer protocol).
Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI conventions.
That is all the critiqued abstract is trying to describe.
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668 
Roseville CA 95747
cbm@rose.hp.com


----- Original Message ----- 
From: "Bob Braden" <braden@ISI.EDU>
To: <sob@harvard.edu>; <mankin@psg.com>
Cc: <ips@ece.cmu.edu>; <ietf@ietf.org>
Sent: Tuesday, February 11, 2003 3:48 PM
Subject: Re: Protocol Action: iSCSI to Proposed Standard


> 
>   *> 
>   *> The IESG has approved publishing the following Internet-Draft
>   *> as a Proposed Standard:
>   *> 
>   *> o iSCSI <draft-ietf-ips-iscsi-20.txt>
>   *> 
>   *> This document is the product of the IP Storage Working Group.
>   *> 
>   *> The IESG contact persons are Allison Mankin and Scott Bradner.
>   *> 
>   *>  
>   *> Technical Summary
>   *>  
>   *>  The Small Computer Systems Interface (SCSI) is a family of
>   *>  protocols for communicating with I/O devices, especially storage
>   *>  devices. SCSI is a client-server architecture. The SCSI protocol
>   *>  has been mapped over various transports, including Parallel SCSI,
> 
> Transports?
> 
> The Webster's New Collegiate Dictionary defines the noun "transport" as
> "strong and often intensely pleasurable emotion".  ;-)
> 
> All the Internet documentation with which I am familiar, as well as the
> OSI reference model, define a "transport layer", but I don't think you
> are suggesting SCSI over IP, etc.
> 
> Can't we please resist terminology pollution?  In the IETF we call these
> [data] link layers.
> 
> Bob Braden
> 
>   *>  IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are
>   *>  I/O specific and have limited distance capabilities. The iSCSI
>   *>  protocol defined in draft-ietf-ips-iscsi describes a means of
>   *>  transporting of the SCSI packets over TCP/IP, providing for an
>   *>  interoperable solution which can take advantage of existing
>   *>  Internet infrastructure, Internet management facilities and
>   *>  address distance limitations. Mapping over TCP ensures that the
>   *>  high volume storage transfers use congestion control.
>   *> 
>   *>  
> 






From owner-ietf@ietf.org  Thu Feb 13 09:53:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13710;
	Thu, 13 Feb 2003 09:53:04 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jKcD-0006fQ-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 09:45:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ixNW-0001rc-00
	for ietf@ran.ietf.org; Wed, 12 Feb 2003 08:56:46 -0500
Received: from d12lmsgate-4.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02545
	for <ietf@ietf.org>; Wed, 12 Feb 2003 08:49:34 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-4.de.ibm.com (8.12.3/8.12.3) with ESMTP id h1CDpqbt054030;
	Wed, 12 Feb 2003 14:51:53 +0100
Received: from d10ml001.telaviv.ibm.com (d10ml001.telaviv.ibm.com [9.148.216.55])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h1CDpopY079784;
	Wed, 12 Feb 2003 14:51:51 +0100
In-Reply-To: <200302112348.XAA03474@gra.isi.edu>
To: Bob Braden <braden@ISI.EDU>
Cc: ietf@ietf.org, ips@ece.cmu.edu, mankin@psg.com, owner-ips@ece.cmu.edu,
        sob@harvard.edu
Subject: Re: Protocol Action: iSCSI to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF4AFD9C99.DD9E5769-ONC2256CCB.004A5D9C-C2256CCB.004C2728@telaviv.ibm.com>
Date: Wed, 12 Feb 2003 15:51:47 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 12/02/2003 15:51:51
Content-Type: multipart/mixed; boundary="=_mixed 004B757DC2256CCB_="
Sender: owner-ietf@ietf.org
Precedence: bulk

--=_mixed 004B757DC2256CCB_=
Content-Type: multipart/alternative; boundary="=_alternative 004B7586C2256CCB_="


--=_alternative 004B7586C2256CCB_=
Content-Type: text/plain; charset="US-ASCII"

Dear Mr. Braden,

iSCSI is in fact SCSI over TCP.   As for the noun - the attached is 
Webster-Collegiate page for transport.
You choose to refer to the definition #9 . English is a richer language 
than my Hebrew - we choose
definitions 4 or 5 that seem to fit.



Respectfully yours,
Julo



Bob Braden <braden@ISI.EDU> 
Sent by: owner-ips@ece.cmu.edu
12/02/03 01:48

To
sob@harvard.edu, mankin@psg.com
cc
ips@ece.cmu.edu, ietf@ietf.org
Subject
Re: Protocol Action: iSCSI to Proposed Standard







  *> 
  *> The IESG has approved publishing the following Internet-Draft
  *> as a Proposed Standard:
  *> 
  *> o iSCSI <draft-ietf-ips-iscsi-20.txt>
  *> 
  *> This document is the product of the IP Storage Working Group.
  *> 
  *> The IESG contact persons are Allison Mankin and Scott Bradner.
  *> 
  *> 
  *> Technical Summary
  *> 
  *>  The Small Computer Systems Interface (SCSI) is a family of
  *>  protocols for communicating with I/O devices, especially storage
  *>  devices. SCSI is a client-server architecture. The SCSI protocol
  *>  has been mapped over various transports, including Parallel SCSI,

Transports?

The Webster's New Collegiate Dictionary defines the noun "transport" as
"strong and often intensely pleasurable emotion".  ;-)

All the Internet documentation with which I am familiar, as well as the
OSI reference model, define a "transport layer", but I don't think you
are suggesting SCSI over IP, etc.

Can't we please resist terminology pollution?  In the IETF we call these
[data] link layers.

Bob Braden

  *>  IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are
  *>  I/O specific and have limited distance capabilities. The iSCSI
  *>  protocol defined in draft-ietf-ips-iscsi describes a means of
  *>  transporting of the SCSI packets over TCP/IP, providing for an
  *>  interoperable solution which can take advantage of existing
  *>  Internet infrastructure, Internet management facilities and
  *>  address distance limitations. Mapping over TCP ensures that the
  *>  high volume storage transfers use congestion control.
  *> 
  *> 


--=_alternative 004B7586C2256CCB_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Dear Mr. Braden,</font>
<br>
<br><font size=2 face="sans-serif">iSCSI is in fact SCSI over TCP. &nbsp;
As for the noun - the attached is Webster-Collegiate page for transport.</font>
<br><font size=2 face="sans-serif">You choose to refer to the definition
#9 . English is a richer language than my Hebrew - we choose</font>
<br><font size=2 face="sans-serif">definitions 4 or 5 that seem to fit.</font>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">Respectfully yours,</font>
<br><font size=2 face="sans-serif">Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Bob Braden &lt;braden@ISI.EDU&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-ips@ece.cmu.edu</font>
<p><font size=1 face="sans-serif">12/02/03 01:48</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">sob@harvard.edu, mankin@psg.com</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">ips@ece.cmu.edu, ietf@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: Protocol Action: iSCSI
to Proposed Standard</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; The IESG has approved publishing the following Internet-Draft<br>
 &nbsp;*&gt; as a Proposed Standard:<br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; o iSCSI &lt;draft-ietf-ips-iscsi-20.txt&gt;<br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; This document is the product of the IP Storage Working Group.<br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; The IESG contact persons are Allison Mankin and Scott Bradner.<br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; &nbsp;<br>
 &nbsp;*&gt; Technical Summary<br>
 &nbsp;*&gt; &nbsp;<br>
 &nbsp;*&gt; &nbsp;The Small Computer Systems Interface (SCSI) is a family
of<br>
 &nbsp;*&gt; &nbsp;protocols for communicating with I/O devices, especially
storage<br>
 &nbsp;*&gt; &nbsp;devices. SCSI is a client-server architecture. The SCSI
protocol<br>
 &nbsp;*&gt; &nbsp;has been mapped over various transports, including Parallel
SCSI,<br>
<br>
Transports?<br>
<br>
The Webster's New Collegiate Dictionary defines the noun &quot;transport&quot;
as<br>
&quot;strong and often intensely pleasurable emotion&quot;. &nbsp;;-)<br>
<br>
All the Internet documentation with which I am familiar, as well as the<br>
OSI reference model, define a &quot;transport layer&quot;, but I don't
think you<br>
are suggesting SCSI over IP, etc.<br>
<br>
Can't we please resist terminology pollution? &nbsp;In the IETF we call
these<br>
[data] link layers.<br>
<br>
Bob Braden<br>
<br>
 &nbsp;*&gt; &nbsp;IPI, IEEE-1394 (firewire) and Fibre Channel. These transports
are<br>
 &nbsp;*&gt; &nbsp;I/O specific and have limited distance capabilities.
The iSCSI<br>
 &nbsp;*&gt; &nbsp;protocol defined in draft-ietf-ips-iscsi describes a
means of<br>
 &nbsp;*&gt; &nbsp;transporting of the SCSI packets over TCP/IP, providing
for an<br>
 &nbsp;*&gt; &nbsp;interoperable solution which can take advantage of existing<br>
 &nbsp;*&gt; &nbsp;Internet infrastructure, Internet management facilities
and<br>
 &nbsp;*&gt; &nbsp;address distance limitations. Mapping over TCP ensures
that the<br>
 &nbsp;*&gt; &nbsp;high volume storage transfers use congestion control.<br>
 &nbsp;*&gt; <br>
 &nbsp;*&gt; &nbsp;<br>
</tt></font>
<br>
--=_alternative 004B7586C2256CCB_=--
--=_mixed 004B757DC2256CCB_=
Content-Type: application/octet-stream; name="transport-def.pdf"
Content-Disposition: attachment; filename="transport-def.pdf"
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

JVBERi0xLjMNJeLjz9MNCjYgMCBvYmoNPDwgDS9MaW5lYXJpemVkIDEgDS9PIDggDS9IIFsgOTUz
IDIwNiBdIA0vTCA4MDA5NiANL0UgNzgxODggDS9OIDEgDS9UIDc5ODU5IA0+PiANZW5kb2JqDSAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB4cmVmDTYgMjYgDTAwMDAwMDAwMTYgMDAwMDAgbg0KMDAwMDAwMDg2NCAwMDAwMCBuDQowMDAw
MDAxMTU5IDAwMDAwIG4NCjAwMDAwMDEzMTAgMDAwMDAgbg0KMDAwMDAwMTUwNiAwMDAwMCBuDQow
MDAwMDAxNzI2IDAwMDAwIG4NCjAwMDAwMDE5NDggMDAwMDAgbg0KMDAwMDAwMjE4NCAwMDAwMCBu
DQowMDAwMDAyNDAwIDAwMDAwIG4NCjAwMDAwMDMxMzEgMDAwMDAgbg0KMDAwMDAwMzM0MyAwMDAw
MCBuDQowMDAwMDAzODI3IDAwMDAwIG4NCjAwMDAwMDQwMTIgMDAwMDAgbg0KMDAwMDAwNDIxNSAw
MDAwMCBuDQowMDAwMDA0MjU0IDAwMDAwIG4NCjAwMDAwMDQ0MjkgMDAwMDAgbg0KMDAwMDAwNDYw
NyAwMDAwMCBuDQowMDAwMDA0OTcxIDAwMDAwIG4NCjAwMDAwMDczNjkgMDAwMDAgbg0KMDAwMDAx
MDA0NiAwMDAwMCBuDQowMDAwMDQwOTQxIDAwMDAwIG4NCjAwMDAwNTEwMTIgMDAwMDAgbg0KMDAw
MDA2NzIzOCAwMDAwMCBuDQowMDAwMDc4MDgwIDAwMDAwIG4NCjAwMDAwMDA5NTMgMDAwMDAgbg0K
MDAwMDAwMTEzOSAwMDAwMCBuDQp0cmFpbGVyDTw8DS9TaXplIDMyDS9JbmZvIDQgMCBSIA0vUm9v
dCA3IDAgUiANL1ByZXYgNzk4NTAgDS9JRFs8MThiOGJiMDU3OWVkNjE0ZTgxZTI0NzU1MzE3OWM0
Nzc+PGIyMmI5YWEyMGJlNmRkMjkyYWI5NDE3YTEzNzdkODAwPl0NPj4Nc3RhcnR4cmVmDTANJSVF
T0YNICAgICANNyAwIG9iag08PCANL1R5cGUgL0NhdGFsb2cgDS9QYWdlcyAzIDAgUiANL01ldGFk
YXRhIDUgMCBSIA0vUGFnZUxhYmVscyAyIDAgUiANPj4gDWVuZG9iag0zMCAwIG9iag08PCAvUyAz
NiAvTCAxMDUgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAzMSAwIFIgPj4gDXN0cmVhbQ0K
SIliYGCQYGBg3snAwMCoc5wBG+CA0gJALAbFDAzqDPwMD5hKWFdwF0gs0HGMYljLXMXkwarAwCDI
oHRgUae5yNxHipbNn7e6JXAegBjAyMBo0ACkmYDYAyDAAO3rELENZW5kc3RyZWFtDWVuZG9iag0z
MSAwIG9iag05NSANZW5kb2JqDTggMCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0vUGFyZW50IDMgMCBS
IA0vUmVzb3VyY2VzIDkgMCBSIA0vQ29udGVudHMgMjMgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNjEy
IDc5MiBdIA0vQ3JvcEJveCBbIDAgMCA2MTIgNzkyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag05
IDAgb2JqDTw8IA0vUHJvY1NldCBbIC9QREYgL1RleHQgXSANL0ZvbnQgPDwgL1RUMiAxNCAwIFIg
L1RUNCAxMiAwIFIgL1RUNiAxNiAwIFIgL1RUOCAyMiAwIFIgL1RUMTAgMTcgMCBSIC9UVDEyIDE4
IDAgUiA+PiANL0V4dEdTdGF0ZSA8PCAvR1MxIDI5IDAgUiA+PiANL0NvbG9yU3BhY2UgPDwgL0Nz
NiAxOSAwIFIgPj4gDT4+IA1lbmRvYmoNMTAgMCBvYmoNPDwgDS9UeXBlIC9Gb250RGVzY3JpcHRv
ciANL0FzY2VudCA4OTEgDS9DYXBIZWlnaHQgMCANL0Rlc2NlbnQgLTIxNiANL0ZsYWdzIDM0IA0v
Rm9udEJCb3ggWyAtNTU4IC0zMDcgMjAzNCAxMDI2IF0gDS9Gb250TmFtZSAvTFBCSEVQK1RpbWVz
TmV3Um9tYW4sQm9sZCANL0l0YWxpY0FuZ2xlIDAgDS9TdGVtViAxMzMgDS9Gb250RmlsZTIgMjcg
MCBSIA0+PiANZW5kb2JqDTExIDAgb2JqDTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2Nl
bnQgODkxIA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50IC0yMTYgDS9GbGFncyA5OCANL0ZvbnRCQm94
IFsgLTQ5OCAtMzA3IDExMjAgMTAyMyBdIA0vRm9udE5hbWUgL0xQQkhJRCtUaW1lc05ld1JvbWFu
LEl0YWxpYyANL0l0YWxpY0FuZ2xlIC0xNSANL1N0ZW1WIDAgDS9Gb250RmlsZTIgMjggMCBSIA0+
PiANZW5kb2JqDTEyIDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1RydWVUeXBlIA0v
Rmlyc3RDaGFyIDk3IA0vTGFzdENoYXIgMTE2IA0vV2lkdGhzIFsgNTU2IDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDYxMSA2MTEgNjExIDAgMzg5IDU1NiAzMzMgXSANL0VuY29kaW5nIC9XaW5BbnNp
RW5jb2RpbmcgDS9CYXNlRm9udCAvTFBCRk1IK0FyaWFsLEJvbGQgDS9Gb250RGVzY3JpcHRvciAx
NSAwIFIgDT4+IA1lbmRvYmoNMTMgMCBvYmoNPDwgDS9UeXBlIC9Gb250RGVzY3JpcHRvciANL0Fz
Y2VudCA4OTEgDS9DYXBIZWlnaHQgNjU2IA0vRGVzY2VudCAtMjE2IA0vRmxhZ3MgMzQgDS9Gb250
QkJveCBbIC01NjggLTMwNyAyMDI4IDEwMDcgXSANL0ZvbnROYW1lIC9MUEJGSkQrVGltZXNOZXdS
b21hbiANL0l0YWxpY0FuZ2xlIDAgDS9TdGVtViA5NCANL0ZvbnRGaWxlMiAyNSAwIFIgDT4+IA1l
bmRvYmoNMTQgMCBvYmoNPDwgDS9UeXBlIC9Gb250IA0vU3VidHlwZSAvVHJ1ZVR5cGUgDS9GaXJz
dENoYXIgMzIgDS9MYXN0Q2hhciAyNDQgDS9XaWR0aHMgWyAyNTAgMCAwIDAgMCAwIDc3OCAwIDMz
MyAzMzMgMCAwIDI1MCAzMzMgMjUwIDAgMCA1MDAgNTAwIDUwMCAwIDUwMCANMCA1MDAgMCA1MDAg
MCAyNzggNTY0IDAgMCAwIDAgNzIyIDAgNjY3IDAgNjExIDAgMCAwIDMzMyAwIDAgNjExIA04ODkg
NzIyIDcyMiA1NTYgMCA2NjcgNTU2IDYxMSAwIDAgMCAwIDcyMiAwIDMzMyAwIDMzMyAwIDAgMCA0
NDQgDTUwMCA0NDQgNTAwIDQ0NCAzMzMgNTAwIDUwMCAyNzggMjc4IDUwMCAyNzggNzc4IDUwMCA1
MDAgNTAwIDAgMzMzIA0zODkgMjc4IDUwMCA1MDAgNzIyIDAgNTAwIDAgMCAwIDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgDTAgMCAwIDAgMCAwIDAgMCAwIDUwMCAwIDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCA3NjAgMCANMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIA0wIDAgMCAwIDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgDTAgMCAwIDAgMCAw
IDAgMCAwIDUwMCBdIA0vRW5jb2RpbmcgL1dpbkFuc2lFbmNvZGluZyANL0Jhc2VGb250IC9MUEJG
SkQrVGltZXNOZXdSb21hbiANL0ZvbnREZXNjcmlwdG9yIDEzIDAgUiANPj4gDWVuZG9iag0xNSAw
IG9iag08PCANL1R5cGUgL0ZvbnREZXNjcmlwdG9yIA0vQXNjZW50IDkwNSANL0NhcEhlaWdodCAw
IA0vRGVzY2VudCAtMjExIA0vRmxhZ3MgMzIgDS9Gb250QkJveCBbIC02MjggLTM3NiAyMDM0IDEw
MTAgXSANL0ZvbnROYW1lIC9MUEJGTUgrQXJpYWwsQm9sZCANL0l0YWxpY0FuZ2xlIDAgDS9TdGVt
ViAxMzMgDS9Gb250RmlsZTIgMjYgMCBSIA0+PiANZW5kb2JqDTE2IDAgb2JqDTw8IA0vVHlwZSAv
Rm9udCANL1N1YnR5cGUgL1RydWVUeXBlIA0vRmlyc3RDaGFyIDMyIA0vTGFzdENoYXIgMTQ5IA0v
V2lkdGhzIFsgMjUwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAyNTAgMCAyNTAgMCA1MDAgNTAwIDUw
MCA1MDAgNTAwIDUwMCA1MDAgDTUwMCA1MDAgNTAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCANMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCA1MDAg
NTU2IDAgMCA0NDQgMCAwIDAgMjc4IDAgMCAyNzggMCA1NTYgDTUwMCA1NTYgMCA0NDQgMzg5IDMz
MyAwIDUwMCAwIDAgNTAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCANMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMCAzNTAgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcgDS9CYXNlRm9u
dCAvTFBCSEVQK1RpbWVzTmV3Um9tYW4sQm9sZCANL0ZvbnREZXNjcmlwdG9yIDEwIDAgUiANPj4g
DWVuZG9iag0xNyAwIG9iag08PCANL1R5cGUgL0ZvbnQgDS9TdWJ0eXBlIC9UcnVlVHlwZSANL0Zp
cnN0Q2hhciAzNCANL0xhc3RDaGFyIDM5IA0vV2lkdGhzIFsgMzQyIDAgMCAwIDAgMjk1IF0gDS9F
bmNvZGluZyAvV2luQW5zaUVuY29kaW5nIA0vQmFzZUZvbnQgL1ZiSEVCIA0vRm9udERlc2NyaXB0
b3IgMjEgMCBSIA0+PiANZW5kb2JqDTE4IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUg
L1RydWVUeXBlIA0vRmlyc3RDaGFyIDk3IA0vTGFzdENoYXIgMTExIA0vV2lkdGhzIFsgNTU2IDAg
MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgNTU2IF0gDS9FbmNvZGluZyAvV2luQW5zaUVuY29kaW5n
IA0vQmFzZUZvbnQgL1ZiTE4gDS9Gb250RGVzY3JpcHRvciAyMCAwIFIgDT4+IA1lbmRvYmoNMTkg
MCBvYmoNWyANL0lDQ0Jhc2VkIDI0IDAgUiANXQ1lbmRvYmoNMjAgMCBvYmoNPDwgDS9UeXBlIC9G
b250RGVzY3JpcHRvciANL0FzY2VudCA4OTEgDS9DYXBIZWlnaHQgMCANL0Rlc2NlbnQgLTIxMCAN
L0ZsYWdzIDMyIA0vRm9udEJCb3ggWyAtNTYgLTIxMCA5NzYgODkxIF0gDS9Gb250TmFtZSAvVmJM
TiANL0l0YWxpY0FuZ2xlIDAgDS9TdGVtViAwIA0+PiANZW5kb2JqDTIxIDAgb2JqDTw8IA0vVHlw
ZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQgODk3IA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50IC0y
MDAgDS9GbGFncyAzMiANL0ZvbnRCQm94IFsgLTI4NiAtMjA1IDE0MTUgOTA1IF0gDS9Gb250TmFt
ZSAvVmJIRUIgDS9JdGFsaWNBbmdsZSAwIA0vU3RlbVYgMCANPj4gDWVuZG9iag0yMiAwIG9iag08
PCANL1R5cGUgL0ZvbnQgDS9TdWJ0eXBlIC9UcnVlVHlwZSANL0ZpcnN0Q2hhciA0NiANL0xhc3RD
aGFyIDExOCANL1dpZHRocyBbIDI1MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIA0wIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAg
MCAwIDAgMCAwIDUwMCAwIDAgNTAwIDQ0NCAwIDAgMCAwIDI3OCANMCAwIDAgNTAwIDUwMCA1MDAg
MCAzODkgMzg5IDI3OCAwIDQ0NCBdIA0vRW5jb2RpbmcgL1dpbkFuc2lFbmNvZGluZyANL0Jhc2VG
b250IC9MUEJISUQrVGltZXNOZXdSb21hbixJdGFsaWMgDS9Gb250RGVzY3JpcHRvciAxMSAwIFIg
DT4+IA1lbmRvYmoNMjMgMCBvYmoNPDwgL0xlbmd0aCAyMzIzIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCkiJxFfdcuO2Fb7XU2By0YIdC0uAAEiOe5N1PJ1mkjQT66bj7AVNU7Y2MqUh
ae/oQbbv0PfrA/T8gBRFaa319qLZiUUAB+fnO794v5i9WyyM0GKxnOlYxUbE8I+/8ljYRKU2htOn
2bur1ouypfNYtGU9e/e3Gy0e2lksFiX++TSTIlp8nCWZcrnJxBy4xF4sfpjhh7ZIRnsuR+Jb+Wvx
UIHoTWSVlcsIznIpdPRh8SNqZVkrY0kg/IA+Pk+VQ21gS2lgHisPJ6gNcQatB126pqjb7abpUCfg
55nfXn+rkix1sEAN8R6rf70AfdMkHSTEJiV6lO9SpQ3AYsQcoDGiqWbL2fvFSEtntMrhP6CNVWYY
vL1QlnECam9SlXgiRkNyVOgWjYgSgKWOYmVk+znKVSrRKNHDFJxnlbc+HRvzuwyGZ8FwlSQuYQoG
KyW6FxXoTE/nc+tHdEnG7hKIaIR2y1Zs/8NfAG9QRMe9JrFN85Em7I7vplISq8faWE20GB6eLlyI
+Tbc0X2EqsTkyRHrzZS1c3GvAPAzCdk5BEKvKBiq42wM2TkdDcWwvBRTZJ3xI4Esrz7CNbWZG+Pv
eosNJw9F7ERJo3Su/ZvRTJKetw3eQ4d5lQAMF9HcqkwivL3rTC8sx2z/CnzH5hrNsQoAQzQ7+Xt0
MURn1jvO2kSPve35DgQfaKVlpybxrJXRzu+FaMcZKg6zeW6Myjx4eG6US7J84nOtxKHumkrSwDXU
C+SfMExdlCkPFgM/gKgsIg/Z1zS7C/EUaY1HLxWYB7+NKOkw0NYv1U4sGzIDCLVP05GcrJeDSYdy
NsDOQEqLTV1FUNSk2K6LskLO3UYU9aZ75P1GiQHN3mi4qbFCodHWToxmn5kzlms/lGMsUWy6jtEa
cBZZnmG0NDuozl4KXn7CIp1JXoSTu/DbdpGVTeTgJDCp6eAhcKzAYjhCqhX8v6kvI9wlVkzZFFvS
4Zm5VKcsJytesTv5H+1uxwrdh03Ut+bvA2Jw1l1R42lLvnrkfTK0igzyQXMvRNVulTi4WuDlbRBW
rBGKkhYbkrwmhBjZEQzZazCMUDhRe5x157Mp0J3EV9pXoOXyOBQ02yPrIEEAFQfgVKIoO8ocXi8j
jfHfNVyOsLXgNrZs3ulWYetB9Fui3IS9l8AU4czkblU/8MYlkPBX3ZPsetblN0WUOxdR6T6iDNuN
+QEOxTiA2lZBVRebJWABexAPsNVgHnmJ5T6F3y1sphJHFTxc0d+a9h641PBd+ET7cf8F7YYg29Hq
4MaFYPFthOUKLxWHUp9LOv9jzPqO7j4zV1ZK0ciBRG/HzJ8NlaE/9dNFIVoKlESutvw7xAqUoYiS
JhysQTMdAgYwQLollGMeT3CrDYSA6CpsPQSebeC4vg/Cqqalev60WuNOLldd0eygmg2i55iEFVBV
XfktAZSeCyDHvRDdZrjOQDsoVjDrQevZrmkADIcVVQkDS2weXJ0d+J9nREvJgnA0Fe890N5jR4vB
4eDWbdGim62swrWKD1pGmsWFxZZXTeCyoQtLbgWBUvBZE/oD84RUpt+w2wVDUHP+Zh03bDHfES2b
1DJFRW0yl2/DXWbnIB+Gzb5UFQBGFqRrlu6CdFBqs6Ry/UyHd2s6XNHfMsL6I5i+QUtM4EUpChYw
9asGHA0uHDj5uSzSw/hiwlgBiqfoqg3WQ4uOQRswkTe87qjqrrichr2aGhR/K9AW0qQq267oVqX4
GGh2lCR3vFiv2pAOlwKa9pjzMy8afB24b2rht1LH1P/V9I0DURInJ/Im5AQHW/3CUVWGaA1RTlFX
h70+XyjuuhCEFH13Ic+Ygu8+0tETDXsHfBg2PIRa2adAYBT6O7Z2EtmrSCLXI8p6Fzh4eQortPgk
VgCT/jqYjmNdhLiuysei5jgGU2Uf7TCSSw7oR47hgld0EIhgDG6pbAIsDiIes+ChrrovpQZTbKlY
Q+0JDA+kVJyCjxXnzz3vCqyDjp2VI649v3Tgd1+VtPoj0FDfCA1P98VprwKLacKlDV9qIruXySTh
tgKUB98ce+QL7eyW24ZODLcR9680fPDPJfUw8fM1avtX8dN0xEtVmhp39PbkwgAzU3gl9i4HCgPE
ibJQCXilU4grK0wOTQ2Uegpv3OLw7drfjPtbGfz48a1B9q2EcQVH1C1OKpOn4ykNTAzIZW/VwMDr
yUwUiCmGZVNNx9osMaNQj/Mh1D27QcBjqixonsFmSalYlLzecI63StxUFW2xE2AIhrcVuAfVUmh8
W9YzSF+fjB2is71DFr99/8vNHJW7XsySGCZ/BN6qXCTwujUCLtgMQm62nL1fHFmcJDCPHWBOhyh1
NKxfUDM4rRywz9ORbjE5TP76j98WvVIWPNMrZcAvU6U8LlAsfSQ+xzBIYqI5VIlYO+R7ZEgKlo/s
IF2StHeKo/FYfjh6dphs/571+14Yu1FTgOmOsrjGYQJGk89QFiahGDM7kNLM3l21XlzdCNb75uoX
4PMjfH1E7Iz4BBqLn8Xth1jcz6xKcmdCGJF13x0qGCPHGJyajutq6D6oSMZDAfSZi0kxBkBSnYx5
i8PwB2OcPkj0NDCmCTWVH9VxfTc+P/+Yy1SWG8Ogmgmob8bTKovjxsiOP5/EyOQQ+nvV8gEkiJBU
3uFLBQf4UyKg8jqj3+KG+b423MrVZyhOqex2OHpoOXWEVmns/Vc6guKWiGo1LTmpzdx58HMQF8ac
o4j+BvDfGqCEDNQURgZGUSxvR8EJ071P9f8lOFMoERnB42KCR7a7ejrtQosN2gUG87BHQ7PJp/UO
6vgrRVIrn9vRIyAO8Fxf3SxgivHy+5sIH4D/JJOusU57LGTae5UJCxlwpo5rp1WC9DA9ZBiWX6jk
KhiDrcGlB+Pd3gmxAGO1xer5w+FWPtpa/OUUOVlHnpL/fhWQIaXZuYzH1QYmeid3EQxQq4dH/O7E
HhPgYgWUeMhz6CnxueYGOintRQ5txRwiMt9XCBYferbOcXbKZR5+xc3qiWbADa/rsI3T6J/ETfn4
zBttB29Yen1csLqogHf5uGcP7yXHsv5elwonsKK+F6uuFetVWcGUY/lZamXTqsH0/w4A/jX4Ewpl
bmRzdHJlYW0NZW5kb2JqDTI0IDAgb2JqDTw8IC9OIDMgL0FsdGVybmF0ZSAvRGV2aWNlUkdCIC9M
ZW5ndGggMjU3NSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpIiZyWeVRTdxbHf2/J
npCVsMNjDVuAsAaQNWxhkR0EUQhJCAESQkjYBUFEBRRFRISqlTLWbXRGT0WdLq5jrQ7WferSA/Uw
6ug4tBbXjp0XOEedTmem0+8f7/c593fv793fvfed8wCgJ6WqtdUwCwCN1qDPSozFFhUUYqQJAAMK
IAIRADJ5rS4tOyEH4JLGS7Ba3An8i55eB5BpvSJMysAw8P+JLdfpDQBAGTgHKJS1cpw7ca6qN+hM
9hmceaWVJoZRE+vxBHG2NLFqnr3nfOY52sQKjVaBsylnnUKjMPFpnFfXGZU4I6k4d9WplfU4X8XZ
pcqoUeP83BSrUcpqAUDpJrtBKS/H2Q9nuj4nS4LzAgDIdNU7XPoOG5QNBtOlJNW6Rr1aVW7A3OUe
mCg0VIwlKeurlAaDMEMmr5TpFZikWqOTaRsBmL/znDim2mJ4kYNFocHBQn8f0TuF+q+bv1Cm3s7T
k8y5nkH8C29tP+dXPQqAeBavzfq3ttItAIyvBMDy5luby/sAMPG+Hb74zn34pnkpNxh0Yb6+9fX1
Pmql3MdU0Df6nw6/QO+8z8d03JvyYHHKMpmxyoCZ6iavrqo26rFanUyuxIQ/HeJfHfjzeXhnKcuU
eqUWj8jDp0ytVeHt1irUBnW1FlNr/1MTf2XYTzQ/17i4Y68Br9gHsC7yAPK3CwDl0gBStA3fgd70
LZWSBzLwNd/h3vzczwn691PhPtOjVq2ai5Nk5WByo75ufs/0WQICoAIm4AErYA+cgTsQAn8QAsJB
NIgHySAd5IACsBTIQTnQAD2oBy2gHXSBHrAebALDYDsYA7vBfnAQjIOPwQnwR3AefAmugVtgEkyD
h2AGPAWvIAgiQQyIC1lBDpAr5AX5Q2IoEoqHUqEsqAAqgVSQFjJCLdAKqAfqh4ahHdBu6PfQUegE
dA66BH0FTUEPoO+glzAC02EebAe7wb6wGI6BU+AceAmsgmvgJrgTXgcPwaPwPvgwfAI+D1+DJ+GH
8CwCEBrCRxwRISJGJEg6UoiUIXqkFelGBpFRZD9yDDmLXEEmkUfIC5SIclEMFaLhaBKai8rRGrQV
7UWH0V3oYfQ0egWdQmfQ1wQGwZbgRQgjSAmLCCpCPaGLMEjYSfiIcIZwjTBNeEokEvlEATGEmEQs
IFYQm4m9xK3EA8TjxEvEu8RZEolkRfIiRZDSSTKSgdRF2kLaR/qMdJk0TXpOppEdyP7kBHIhWUvu
IA+S95A/JV8m3yO/orAorpQwSjpFQWmk9FHGKMcoFynTlFdUNlVAjaDmUCuo7dQh6n7qGept6hMa
jeZEC6Vl0tS05bQh2u9on9OmaC/oHLonXUIvohvp6+gf0o/Tv6I/YTAYboxoRiHDwFjH2M04xfia
8dyMa+ZjJjVTmLWZjZgdNrts9phJYboyY5hLmU3MQeYh5kXmIxaF5caSsGSsVtYI6yjrBmuWzWWL
2OlsDbuXvYd9jn2fQ+K4ceI5Ck4n5wPOKc5dLsJ15kq4cu4K7hj3DHeaR+QJeFJeBa+H91veBG/G
nGMeaJ5n3mA+Yv6J+SQf4bvxpfwqfh//IP86/6WFnUWMhdJijcV+i8sWzyxtLKMtlZbdlgcsr1m+
tMKs4q0qrTZYjVvdsUatPa0zreutt1mfsX5kw7MJt5HbdNsctLlpC9t62mbZNtt+YHvBdtbO3i7R
Tme3xe6U3SN7vn20fYX9gP2n9g8cuA6RDmqHAYfPHP6KmWMxWBU2hJ3GZhxtHZMcjY47HCccXzkJ
nHKdOpwOON1xpjqLncucB5xPOs+4OLikubS47HW56UpxFbuWu252Pev6zE3glu+2ym3c7b7AUiAV
NAn2Cm67M9yj3GvcR92vehA9xB6VHls9vvSEPYM8yz1HPC96wV7BXmqvrV6XvAneod5a71HvG0K6
MEZYJ9wrnPLh+6T6dPiM+zz2dfEt9N3ge9b3tV+QX5XfmN8tEUeULOoQHRN95+/pL/cf8b8awAhI
CGgLOBLwbaBXoDJwW+Cfg7hBaUGrgk4G/SM4JFgfvD/4QYhLSEnIeyE3xDxxhrhX/HkoITQ2tC30
49AXYcFhhrCDYX8PF4ZXhu8Jv79AsEC5YGzB3QinCFnEjojJSCyyJPL9yMkoxyhZ1GjUN9HO0Yro
ndH3YjxiKmL2xTyO9YvVx34U+0wSJlkmOR6HxCXGdcdNxHPic+OH479OcEpQJexNmEkMSmxOPJ5E
SEpJ2pB0Q2onlUt3S2eSQ5KXJZ9OoadkpwynfJPqmapPPZYGpyWnbUy7vdB1oXbheDpIl6ZvTL+T
IcioyfhDJjEzI3Mk8y9ZoqyWrLPZ3Ozi7D3ZT3Nic/pybuW65xpzT+Yx84ryduc9y4/L78+fXOS7
aNmi8wXWBeqCI4WkwrzCnYWzi+MXb1o8XRRU1FV0fYlgScOSc0utl1Yt/aSYWSwrPlRCKMkv2VPy
gyxdNiqbLZWWvlc6I5fIN8sfKqIVA4oHyghlv/JeWURZf9l9VYRqo+pBeVT5YPkjtUQ9rP62Iqli
e8WzyvTKDyt/rMqvOqAha0o0R7UcbaX2dLV9dUP1JZ2Xrks3WRNWs6lmRp+i31kL1S6pPWLg4T9T
F4zuxpXGqbrIupG65/V59Yca2A3ahguNno1rGu81JTT9phltljefbHFsaW+ZWhazbEcr1FraerLN
ua2zbXp54vJd7dT2yvY/dfh19Hd8vyJ/xbFOu87lnXdXJq7c22XWpe+6sSp81fbV6Gr16ok1AWu2
rHndrej+osevZ7Dnh1557xdrRWuH1v64rmzdRF9w37b1xPXa9dc3RG3Y1c/ub+q/uzFt4+EBbKB7
4PtNxZvODQYObt9M3WzcPDmU+k8ApAFb/pi4mSSZkJn8mmia1ZtCm6+cHJyJnPedZJ3SnkCerp8d
n4uf+qBpoNihR6G2oiailqMGo3aj5qRWpMelOKWpphqmi6b9p26n4KhSqMSpN6mpqhyqj6sCq3Wr
6axcrNCtRK24ri2uoa8Wr4uwALB1sOqxYLHWskuywrM4s660JbSctRO1irYBtnm28Ldot+C4WbjR
uUq5wro7urW7LrunvCG8m70VvY++Cr6Evv+/er/1wHDA7MFnwePCX8Lbw1jD1MRRxM7FS8XIxkbG
w8dBx7/IPci8yTrJuco4yrfLNsu2zDXMtc01zbXONs62zzfPuNA50LrRPNG+0j/SwdNE08bUSdTL
1U7V0dZV1tjXXNfg2GTY6Nls2fHadtr724DcBdyK3RDdlt4c3qLfKd+v4DbgveFE4cziU+Lb42Pj
6+Rz5PzlhOYN5pbnH+ep6DLovOlG6dDqW+rl63Dr++yG7RHtnO4o7rTvQO/M8Fjw5fFy8f/yjPMZ
86f0NPTC9VD13vZt9vv3ivgZ+Kj5OPnH+lf65/t3/Af8mP0p/br+S/7c/23//wIMAPeE8/sKZW5k
c3RyZWFtDWVuZG9iag0yNSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDMw
ODA0IC9MZW5ndGgxIDQ5MzQ0ID4+IA1zdHJlYW0NCkiJXFUJUJRHFv5ed/8zCPFEGOLFwMihgBzB
CwkSYRDFAw8U3EQZVC5BRjyirokaolLgkbjEo0qJriGQ4JrBrEaNa9BVN8Z4xds1ohWNx66ua0zK
LWF6H2x2K9n56p963f26+3uvX38NAtAeyyCRPnZCZExOWuYjoHEQ946ZXuxwjjx8rxY4uBOg5ukL
5ll/KL22nMeuA+bjuc684j9/2JNX8PgAMEXnFS3K9b0cfxSIcQHzM/NnOmacniR78nrlPGdAPnd4
9+ncCHS4wu3e+cXzFhaXxbRwuxnouq2oZLpDJCx3AnUe3P6g2LHQ6VVNv+P5fuxvne0onulTP3UV
cOhL5pPuLJk7j3nz71Bd67izdKbz9qAq5mLbAnT0NtYCxij489dDVqE7oG/xd5u/e+6RutmYBZu7
UN+U3jz7Dz9/QBA24H30xmOKxhE0YiQ+xCtIRxWG4ww+QQcsopNQsCEZdQgifwikwEIGNuMqXkUp
7uAmQpGGG9SF17HDCV8M1vf5Pw3lej97eSIJu3CAimgCItlOFeEUxjuv042wIFSf0le4tRV3qLdu
QCpb36MzQrAU76ILCvGVbm7NIHJQS0voPgKQjUoVqyr0LAzBHlykNLZGY5Fxpd0eFPGsHWShRt2k
7+KQIszkld5COTPejUbRTyYZ22BFMF7GGDh49Le4St4ULRN1iB6mN3NvLZ6IMHFcmplHGEZgGtZg
O2fjEm7jR/Ki/rSV6hnn6JHRerppmI/FXFdbOXu12In9FE3RwiIsnC0L+iCDx9ahhvf/FGcpjbKo
kQ7LGiPKPVR31T76rtboi0xm+D4O8x5PKYp9eAcZKOepXmqeEdOynCOcgS04i3PM4wbn/Uc8o76M
W+JNsVRP1nX6DnPxgD8GYRymoAQL8Dp+z6d6BEfxT3ou2rHnGXXMWGw81us5t8EYxtzHsvcEXruS
T2k39jEucZSdycpRDKIxNJ7yaB1toH10la4KkwgQc8QD6ZIn5XU1wDB0HK/ki168rw2Tkc8n8CZn
ez3HW4djOEE+FEwRHNElnv+TGCKSGTvEGXFDrpDrVLOx0n3T/Tf3c10BM1fZcM7DfHzMWfgH+TKH
PlRIc+k7Zv6O+KPsIDtJm+wvX5ETZZYsl1XyS3lalap6dc0YYTiMerPDPdt9TqfptzkXBBPzCkE4
YjGQ6yeXq2kW83MySrEEy1GBtVwv67EN9Rz3FziBi/gWf+cTAAUw5wLevZirbgWtZWymnXSYjtEJ
ukU/tUIEMkLFADFUJIkUkSdWMKrEWXFJ3JM95HS5VC5jVMu98qqCUkobMYxUo9KoNZ00h5pTzTke
Xzc/bOnbktVyww13N/dv3Bvch9139SS9iPkHIQL9mOkqZrmZa7CG8TFX4l4cx9e43Mb1CQkyuOL9
yMbVEM6nNpSG0wjGaBrHyGBMpikMB+VQPmMpLaO3qIzepjX0Xhs2cWw19BHtZXxGBxgXqYm+pwf0
RHARC8nVHCRCRKQYzJEmieFirBjPyBMlDKcoFQv4hGrFp2K/uCS9ZZCMkA45R26Wu+QReUH+SwkV
riJVvJqk8lSZOqPOqSvqueFv2I18o9o4YupuijVlmApNm0yfmO6Zms0mc7o5x7zEfMGsPYJYrf7C
ce/BL3+RpjM01+iqFoomvhd+0mmsogzOmElMlEVyrfzGyKXH0krXqEIWyFl6h0wRz2QJTRJfUKD0
N+JkLlZDU724JZ6Ku8qHJor7FKrepc9EiUwSptZNjPPKR5UZ9wBxGXHiDWoUx2SZLNN/QpxRTU1G
tTgHq7opvNHEt3qV2MiTTosCUYlMFWs8RwHn/SNjIec7QZRTX3lBVeOOtIkf6DFtYNU4RSNVbzFV
DKZ6VtwW6oWHNAdOeg+J9Dl9S/tAVCdraZR4gU/LJdrTQH6ETskAuiA9kdXKkYKFD6WLxyJDHjSd
lf2JWCW+wWKSFMW189+fG7P5BlSJENY0O6vJeYqBHzay3j91H2xVbOOKUcl1tl2GYzyi8Jo4iTi+
G3cYmViJGBzgGixHlNiEJXoZzWDdH836KbCPChFJXqyWFua2lN8LXxHIWjiNd33G+v8Vq34aPcLr
ZOWb1YhQ1TqyWtlZmbJZfysZM/Aat7ZgvWmPcR5jyQIoq7uaq/w6pvKb8x3v3w3xzG8KtqtwZm1l
ZZ7DM7a4U5HIWImTJPAGc07ge56uUll5N+hCjrCA36hR/CaeQIHeiCQ+u/G6TFdimt6uX0UeJug6
1t8FejcGYJWRJSYZYSqWNfYEHeX36K9UybqdimusR0HkhweMXcwowfgcFeoya+dQvVpfhA/nI5Az
lMOv6G0U4xHnLVU24iX3GNGgU6STX6gmjNO12p88ka+LWHkPosZssPYsQy+jhmsXicMyJiYOTXg5
fkjc4EEDB/SPfSkmOiqyX0R4WN8+oSHBQb1tgQFW/149e3Tv9qKfxberd5fOnTp2aP+Cl2c7D7PJ
UFIQwu22lGyrKzjbpYJtqakRrW2bgzscv+jIdlm5K+XXPi5rdpub9deeieyZ+3+eif/xTPyfJ3Wy
xiM+Itxqt1ldp5Jt1n00ZVwm22uSbVlW18M2e3Sb/U6b3Z7tgACeYLX75SdbXZRttbtSFuRX2LOT
ebkGL88kW9JMz4hwNHh6senFlsticzaQJYHaDGGxxzUIeLRnUq5utmS760VbcisDlwyyO2a40sdl
2pO7BwRkRYS7KGm6LccF2zBXx7A2l3+zXi3AUV1l+L/n3H2UJmQT3kmgu7lsMC/CQx4JAiub3QaC
bfMg7MZUNxA6QLTF4VHRTgnTBugCWqp2KEMZhtEOQ7TchFYTnWHCOB1GHayOE5g+1EqLirbQYcAZ
6Jjr95+7d9lsUdAxk2//c/7/PP7zn++c/1wKq2lMd9j0qGn8G3g1tNffVzmU3DfgozWJipxOo7Oj
PWbKjjjPkV+BeevMSd/4YPLtKgYvCMd2Z1qLZDIyeYOfq8nkbr95tDGWaQ3wbzyOMUwRjCaSUUy8
DyFsaPZjLtETj5laDyb08zp4Tfbq1hkR1iQ2+s37jGXG+uTGBDamMGlS0/ZAf2FhaNB6jwoj/mRL
zAiYS4uMeEddcd94SjZtPzUl5J8y2lJV2efLt8PaNzYvVcjJzSysS9tUSTXnUkNTOq4ae2QsBx1M
/1o/PIkZWNNC/lm3kJJrF6IZ/uIaepmd2I8N5n3hRNJXC72P+5uuoM/wJ28Q9t/46MPRmo6Uxh30
3SAuMkvSRIPdKZsVFWZ5ORPEE8aOwsclqj6vqnLbgDCNTT4/BMJHjyC2HfHaagQ/EODt3TsQojWo
mN2NMbvupzVF/RSqroibIsGWIccyYRVbuh1LunvCAI9fI/6+mGB6S9P/eb6J4yLra01t4n8wr7Pt
Dc1GQ2NbzB9JJlKxbWgZVbPtC9O2VEmzDQi4qQcRqeUGqNfUFmMF/l3BqBHZkKjHUYOP5rhwTBaJ
uF0SRVINBf62p0fmSiyHx9KDbsX/zgGPFwRWGs0fNX2Jevs3PiYQuMdOA9bH3EuJ291SazJrK0bX
F42qj3IvJynhsF4qGlrakskxo2xRXFbJZNTwR5OJZMeA1b3G8PuM5KCMyVhyUyThbP+A9dO9RWZ0
XxyLWK/VgtqClvUZ2p7GvpC2p7ktNujDJ9aelli/0EQ4sSzeNx222KAf97PSCtaykit+riC/4VT0
C69qXzQYIupWVl0pVH3tgEZK53V0Gq0dELbO5+gEdLqtCykd//FNEW6JZXJAHax4lXoA4As1MBKh
1T76ZMtIk69WUS3jz/UZd41WzCXhAC9sWUc9Or4Bga+4T1C9uwar+Bo1wtYCzIT+gP4MBdH+cdSb
IQ+IGpLQrwA+BiqBZsAPrAFiwErgKaARbU3gWzyGA7mf2j1fog7XWfK5WqkEWIGyob9P5fpmCqBc
z3XMN1dOpXKUS2Ar80xF27PWJbajXYlq14p+m6kb9iWo3w8UePZTEWQeMA76QoxznH2GbJBneK3W
VZS3wY/lKH8CGYWvdZAroX8Y5cVALvp8TtRYa1HOR3kxYpOPcg4QQb+b3Aftc+FjJ+zjURfcFvPm
QhZxW4xZJi9oRdohvKkuUJ/eQuNhH6uAdfOanTWx/+zTv0GU/cuE7Z8C+ypu+/YpiCysk3PVXu1M
rfWwOEeb5FHrGsqGezxFGJ4LNA3r+xCo0Ttpimeq9Vf4uNz1Gs1D3QtMVuAxD9MueZ1CsFW4XwRv
OmmJmA3DPOuW+CZNdQfpQawX8aYZ8D3O3AMXpqNds+rfSdP0S1SIcojhJfpzOk6IDfa+ATKMuF/x
kvURxggzMM4gcAb9J2H+ao4B77vWOtKLtpdhexLYDI5MASbBvldxGH24P+b5PM9h7wP5FAcB5h4w
x0Fqfxzc70DF/4TCRGASsADgeV8EfgY8BHyX22DciWg/DX48zZxhbjI/mBuK/+CT4izv42bEhjlm
n5kfiMdoDzAeqMRHya4UytFWnRfeR/aZzwKPzdxizjgS9lKb99pVXidzKkMarko1tzqDzK0MWcbc
ZylDag1lYojmM2ftWDtS+RDh88hnwpGOP3w+1RmBlF00jmPH++5IJxZpeZSCsK10vUUP6rNptXwD
/G9H+RHIBYjPEXUGr+rfow9EDwnPEFViL/nsvpQlDzI8w9pGjDeEWJbq5+glJYdFiT6suVy91mVX
r3jahlPOlNnQhmwbS0am7b/V/y8Q51299BjKf3MNW5Y+TC9greT5uzYL8DsS+n6gGyj3VmgHvV3a
gGcV+cCb68ATegjfryFaoA/RUn2COndB6Fdh7Gq9ixahn8SX2nNyFR1z99Jn5TD2EXOJ8/QMg8eH
3JTmUTbnPs0lJR2+3kHyGch1pDpTNdYf1Lmqsf6ozmSNNWJLquHcwPezyg+k7uZ8h69pXr5MpfJG
Bj+zeJrBz0Xo58vmZYYcyzKVW3Kdc4o+EznX8PrV/diqzpO652Drd9pny3T/EzQgTljvqHv4HLU5
5xqYDQRh/3nqHsE9jP3mnLnfanc/abXLFVY71vlj927Ia9YpMcPqS+fUIM1J3WWFTi7lOLnOUXE6
jwbp4dR9FuR8qh9HDrfz6DiVP/9Ck13X1N02R/nL55DPYDXuvRnI4/+wbukF9Lh8jkjiXLIeHGlk
m+6lCfJPuHNX0BZ5xPqdPKDuoIgcobiswBlGX8RssktQsauOGtCH1HjcBpJ17L9bBz/5LqhHHXvl
3Mu89+5blAvMcF3BfdSKNifUWoPqHj9I0zkOqu9W5BWM5amgAl1QRapNUPX5Kt4LKh64AzNikcrN
S3hMd5PibJ7qM9e65S2gGobrFZqP+YNqrnqq9dZQqavVuqLeFQX0kDxLs2Q9PYByoeL9buSoMuTL
euRHQL4PjICbPruucrWS1k2V73eofJ7jqqbV6j3BNjdNc5fRTIZuwJagKvkKxnkCvLqF8quWpd4H
v6d8nhv6aOp9wu8Eoc7Lb9HvF1TFZ4x9UPmG/TkEvr1JD3BO9BxDDMfwGdQ0xLs4lQcLUBeQ387A
8yldsS21gHiLWpWthd4Tp8VJcdrq4negfJu+LL+P/TtJAdmG/P0GcuMi5PAViNVvKCZ/jXIJ9EeA
bXj7baE8PY865UW0mwPbJvQ7hzGOwc7YhT7vQr5Ki+UvaYMcwvvgIr8RKKBvhXwUqKOw9kPqEjep
yz0fOXmR9bIan7HF+qLCMeTNi6m+KShfHdzJ5+14293BX+Vrpp/s4x384zF4XNUPbXSd8oisd4Gg
LUcaxX7qBY6Kt9H2C7RdO45n/mGKapeAwyn8iOqV7AMaccbmaU8BM/V59BNgJ8qVkKeBk3adDgHv
AD0Y+wzkKTc+FRhiGfgMCd0R4CDwK8eWCZ7rTvpMuIpodP116mZo161/MrLb6ztpPuabry8mYsjL
9DzDvYPaPNuoTeJ+0KdhzKw65pmjv04b7+bP3aC9SbNUDG2E7mWN9wo+u5yf/1/j3SuwvzuAR5UP
V3Af2xwaq52nEshWyFa5lb7OQL0K9bgTT+06uMY4Tt9R+vT+2XpwhSTn7Cx9dj17X+9WF6fw1s2A
w4M0H16gZxn6UrT/F/dVGxTVdYbPuefu3V3Xy66IRkE4wO5VkDXgWoMf2+xdAho+JmC0CrSTpVrj
1OiA1SbTFIpOY6qNFhqNGm2EpKHpBCjLXTWL2sqkYzJmMkpnOtNOfyi29ld/lCStnbQofc7ZXUSj
k3Sm/dPded7nvB/nPeeee+697wHu1R2XyAsC2kX4Ln5WV9/6HDSiRjku50TkHrtH12rJdgHFh7lm
yj4HBCb1KzhrACJW9tfJQQH57ALKKfJNgUn/UvKSwJR1fUSsK8aU/tT9Sd2Xe+8P5meql4FG1LOX
SQl4LTic4sn9nXxf3LXn1yT2+6Qu3iV/vifmzjNx59nAs/KgnP9PwLPzAfA+8N7/eiyK94N4R3gA
WaOuJBXaUtSe6wmOq7c+JGQ8AzwT3wU8eeOjaP8W7Y1AEdrvwHYMvA+MNOO3YZ/AdwRb6fZJNRP1
OyH7AOS43ZLoe+sm8Fwix61zhPzr90nsSvQfPwCsgg+7cPwUgN07/gugHH1SeX4MfQf419BXJ3KN
o33rOvADoBo4muDxHwLC78QYvxP1yH3Oof9VftD544ty8pwRTPFnzhD/Ca/8QnzXmSN1/z+PU2eJ
+7Bch+T8tSnzedAZ5y7G/nFOBWppr6gpRR0talkb6mdRP06yOLc9LnlmMk+K3eIbKGpnUb/alqBm
1uQ8iqacByvOknUTw+x6rKIiYMbBRQ9LtgoKA0PCYWXOC/ySXVf6yALCYbhmzc6SnqtWWVmy8ciy
RCO2cFHgWngau0r+CijsKrtGChK9YgUPB8bCOgyUfY+4KSWcdKNejgIKMdkfYr75ga4L7EP4P2CX
yDdkt0uWPiOAhO+zd0g66uoz7HTSczqWNiNAwjtxKZQMQ44Ao8AYoJJm9hZpBzqAAQCFHiQHioFa
YWG9rBfz7EF/N2Qx0Ax0ACpZx96G/Rkh2c/ZVpKPvgfYYTIL/BI7JPlNcCb4DdhzwK9DF9yV1E+A
hf940v4q9NngY0k+CnsW+Ah0wa8k9Wfx6RH9diW5m+20crgnnAN/LlACMLQOo3UYS3dY1ASQlH2f
bZMjDYID4O0JxnK1WXleeY/aYg/NDXRjSduw9G1YuTasXBtR4WpNxbQmYhaxVsS0IqYVMa1YlRK2
E+PtFJsU0gPkAgzrvhPrLuxRyGFgRNpfgOwEuoXGnsM6FmJW+9lWq4Bjk22JLTcDoXPsaSy1yZ6O
zc0OdNzRnNPERgSnJdktYjdL7+aYc7qwbo5lZicYUc+E09gm8l1AIRmQPuBLQDmgsk2Wr5ifZU+Q
7Q5ipvF2pZ21q+02taScpl9gAVKHNzgn6WwRCSKgkEeCtLTJ2eLc7WQeZ66zxGk665y2ZtbOOhjj
rJiFWC2LMFt8Ytiyr1gCMldrK5Z0urpdUdewa8Rli2rD2og2qo1ptlytRDO1Oq1Ja9F2a51at+bs
1DrtSpOrxbXbxTyuXFeJy3TVuWzcTrvDe9lG8W2C9AAtQCegYo0jsOeyp4AI7kYES/GUqHQhCTQP
MIL2KNgGzY04N+LcsLphdcNKIIWnDmgCWpJebdKT6iPix4QHEEVRGqxpWNtRyDHRAqqg6dB0aDqi
RpRxzNADmQvUAUzaRgHsGsiUryTpbwI06R+TMSmfKfoq4+bXFwwX0mgh7S6knYXUDIbCATMfIj09
PeKNGJGCSI/a7G02mguae9Rab61RW1Dbo4a8ISNUEOpRi73FRnFBcY/KvdzgBbxH7agZqLlQc6VG
jdQ017TXsFLcuphVVBKQnG8IPm3NzQyUusMrcQKlJALZBVwDGOGQxUAIaAZUZQCSK/2w9sPaT2qB
CGBDj37xeoHkSZ+wd0mfaAm/cpef4cL7rBVLasNVeOVGgC6AIXcf/H0yOtEakPYo5Ki01ybju6Wd
Q6b6MLzgGuVrrhGPXyMJARGgBbCRK2wDuQYgMyQHWoABQGWN+G9gG5R+/PuUPuY39cWzOJk9GwVT
+gyHJ+xRpmMP6CiyhTwm5X4pQ1L6zLQq/WaV/qsq/cUqfQEaSgEJw3FYyjzTFdZPhfXasF4Y1pHt
IZJHdGWWlJqQ9C9SPiGl38zI0z/N0z/J0z/K01/L03fk6V/OE/3m4dnVlQwpXULSI1JWSTnfdHH9
Pa5v4Hop18M6PUkxOimTMkfKLCHpx6fc5W7iPEc/JuXIRK1gIY8rRBKdsIJh0G0ruBp0ywqeBP3T
Ch7i5+mnVH7S6E3Ld4OHZ9G/0UpV6J8k+SNaSXrBY+At4J+RIDXAb1rBPSL+p+h/HPobJN8h4l8n
dbJfF62U9teS/X5i+Tdi1BOW/zsY9Tjxy1GPWv4bsB6y/PtBL1v+baAOyxAT3GoFF/LwDLqF+BQR
u4kYiphJTXLEx5F5G3h1onOF5Re9ysUAcfqY5V0MWiBmeZ56SZ0cjlteeZHZxCtTzCNeOeksYkhO
o245eZ3kS3ZY3j3Iop0ybvB/BM+JCyd/p27rJP/TeVzfeqh/pJVWL//NkFgui1/xx6lxhl/2nuMX
fXG63uLD/rgDjgv+uEJP80EschSxCj3DB/xbeL9Xenu88OJWdwUX8RPeRv6qAd3ie/znxTTIdlzx
ergb/I/ymmAvX2XEKdxmEIOZ0/gK77f4cpiXxWllrJcv9sXFVEqQo/cMX4gR53vlVL5SelZZSuz0
26bfvsu+0b7evsa+0r7Evsiea8+2z7NnONIdHkeaY7pjmsPh0ByqQ3EQR0Z8YtTEoYGSDM0jSFOF
VGXbowgJId76CnUoeHaiM1m1Ur22jEbTq0n1urJoaVF13D7xZHRZUXXUUffV+kFKf9QALarsi1Oy
rh4bVJj2ZkXTH6sfIpQW7z2YJbh178GGBlodHd5EqjfmRm+uxXVMW9MYtXnL5pDZz4bmhNIfnbF8
Vfl9RFNSFt35zSma+puTHT1SvbY++nZ2QzQgGhPZDdXR1Wtzv1Y/pOxQmivKh5QWQQ31Q/R5ZUfF
k8JOny9vmAwj+UoLwlDxtyTCYiRfhJF8GpNhNTIM2zS/onwwPz8R9C6tFEHYPu/KoC2JXD4MgVx1
ghCm5BCfzOVTckQY9kMimXtqsumEumUy93Qik80TQYOGgRC/IUIGSw0EDBql0t17x+01EtNpIIYc
x6ANcpx/s160QVFd13vv232Pxy77wX69Bwj74S6FJwgLuwo+4C2wGt1ATbANS1xZBBR1CiJsUj8h
MdGR1qBtR23HFtpakoyZuohJdrANGWtqzEyHTNt0JhlnYlOmP9ruaFtjapW15+4yyWTqn870zTvn
3HfPefece865552H8RcyX8nIQBYsyZAskJH+n1dv4/8gjGe6bvR0B3tdwagr2AsQjX/rmT4hPrrV
bp/uuUEZ9jjjiW7t7qO0qzd+w9XbHO9xNdunu7ofwe6m7C5X8zTqDm5qn+5WepsvdildQVdXc3hm
aqQp9CVdxz7X1TTyiMVG6GJNVNdU6BHsEGVPUV0hqitEdU0pU2ldoScbcWhj+3QWagw3bc7QGaLJ
hvMQzXeEG62G3fXpw7HGIRzKn1Uh+GxppHBc62qM5wBQVlmgLEBZcDopSwfT+iWWcGiNI38Wv7LE
MsC00dWIJCQEdzR/fg8NDQ1TiMUkwMMxIT03DIfW0RaKr32ioz0ux+VgXIk2hzENR2zpampXDHPy
vEwG5BF5XJ6QL8jqWCwM07lzznkn6XQOOEec484J5wUnSxmb299Q5AnnLScTg2zCw3AFm9M6Y0Dh
po/DsSF6IVAwBJBRJ8WkpvaAE3VDt4uhMy9DJgAXQBVAG4Aa/Qrw7wD+BPBPABU6DPi7AD8FmKEz
TBlTFhR2NFONYYkWHYHxzlT4vKsTQLu2ZWhbR4YGWzNUDngFoBcbqrIDemi8MZoF/B7ARwB/Afg3
gJrxMt704rFM1oaH0JCEwXwED8MUDUnDWIIBpu4eHpIkRIEmOEQARCX85bxHeCiGwBUQECAglJ4d
oq/FKP1CEGow1GJ1ultGHGqZJvgyeQvaVI7MXURqVYK8dYlB2RwdvI6RmMWq54BPEINLEI934S1I
kAx35UW51XBHblmUUQOMDQ8AVVY4jA6jGxAUf/TAzrz9QFGj+8iueht0hR7+UX1fvQtVojq0HocV
DwrdDBFDCLM6Pl9jt+ry7WKAXVc6kA/tbtVA4758VuXFIdq5mq3VlCordLnVJUpVcUWoqXgrFy2I
lkS9vXW7vcN1H9m12hzJxNZ7AyUF2hxSyrIJ/LjirC8w19cXMKoV5WUVKzlcVVDKrpDqTQGerzyD
yBn45CeYJy6tXuti+AQZUTSGdfNWq0FTCV5K4IoZFPSwv4SGpR5fQyIqIb9+s6ChKGSz5eUk8GHF
JBZ5sOe5qA/7Lq+ZHijaXUSgFShT8pvlTnFAHBHHxQnxgjgnzosfi7fEbFHcANXz8IxjUwd8aVrv
RFqSdyL03mNYbA32Nv+5xXAnSe+74FDqV0PSkGxI3knTXFsNBjiqK5cOGq5iY24N3GkwXK+swBEI
7WAER/YMYoeFZQlntVZ5/atsLOtyeorT2FftX+UBvMpf5bVazCxntfl91cWeYrcfqMflZC1mq8lD
pWEAb6ss+NxTbfH+8LfXBaNmt/vcN558tefAtcGfXfn57ZXOQ1sPPnvqZGJkLF5oLUk9f2B/uPGp
sPM3L2yr++besVhDjNnh5hpSV8b62kLr848fCe/s/1p8396/P9f3Yt35jrXHt++c7PzkF789Ub48
X61Zc2rzY1v21lbuXRQvTe0PTnXt+omXNgybUhvIAfVLyIRqFdcp48tGckR7zEiyz/BGdAabIJOz
+Vd0zo0sZkfNm7bQxIwkF+W098BzlRUIXIItnmIP8RnQKuoYi9lWSMiB070nzmLv3f0/anXkbTiY
GnA/vu0kHvs99uOH/aXNf0udeucPF8Ze/gHYUA42fD1tQ42yvERVmvWYmgHlRjDCBB0Inw0G2NkK
VmEZdtTSfu6/jcARk89qs+ZaDIjz+f254PRyUn6md/xsav6z/RMtDjF0QN1TGtr2ndSzH6TeS+F+
d/CveNc7H8THpqgF/anz8PvxLrKhNqU4TMK2q1aGt0XF90WGx4hTqfRZueiNXEWrUdXqLUWWUQtj
SeBSaAf1nXqiF4WzYBSc1kjLYiQJNi3k1kD+2GqoZXjQ5POn08Dl5JayJJMe/dsHeY7TuHPNlbUh
f+P28dT5Fc7xjaYc3szXVlWuHercPk1j1IZHSTv83DCoQbET9eiyHv+IGtOWL84wiBjwRhzFJ/Ak
fh+zcKiqX0ejKnoAIMsj1Ecrk4DTGWxyWBxtRL14n9hO05VPPlzAA+gK0iBJKUAKq2EUXqn18UqD
r5PHE/wFnvAvanfuo2sN7pEkurfKCnfa+sxOMFqpBMrLA4EraVy+UqHr3obSx6r7kBWdVsyKEBUm
hZuCCgmKQJ5BRxDRBUx4B/wz8XgSOaHu0XEWjF3w8r+QHu9AVphB+B8K/A3oCU+wms/SEgbN4s9A
fL2Sq9PpFaOvQj+iP6Gf1Kv0om2WLMcLKBMGSW4xJBfSJ7xBNtJg1KBPkw/wp5KUztjBiMldZTRb
rTaLw1dPfEaIDg3PbbzBYZI3p0h0tTWbc+e5G1XXfnz/6J7VhcTtJssq95Eb3yu1FxbRPa6APZ6H
PRbiPuV5TtDU2ISCumpBASRSpC+0Wks4mVvPvcqxiv1pVUfW07YOYVfWsHE496zmh7rvG1/TvKa7
rr5ue1f40PahcNN+T3XPZoE/I5WozreIVtG2TOB4m0bQLKsW14nHbON2ThAJseWJWpHNYUSiZgUb
xIIzqaBc9ik8r5i1DaM85hNMlaI1qPPGRUwLJBFnmSpw3PEZTLSFCXxcyUHsJ181dZoGTCMmlSmB
OcWkwKbykF2xj9qZqH3STuziZXwPsi4HK4q5kwyQETJO5sg8+ZjcIllELJrFL0EaLmX+gpxsNUQG
70ZaoN4aIFPk5GJkUG5YHJxmSdOm9jfHeTzHz/MERQbD0gI9HunIQH0lhozIpYPicRH4YZ181KA+
eFV3FbJ2cE8EIkY/rBJmHD6EMpWUc/kzx4hjOcI5/kN3tQY3cZ3R+93du9LqtStLtmQ9VlrLsiyE
JYOFHRMPvhhKGiDYDCXGKQ6OSIILFGw3BAxDbRNa82phktAk46lxm0Ig+VFsx0Z2UpJ0KBNoUugr
gcnQuK6bQoM66YROy8Omd1cukzbTq72PvTPa2f3Od8537uzy8grutTV3xuAxCPZuevxIUTj/Qs/R
K6WLj92cB6mN9Ys8QKZuh6EGXjzRdWxL68jZ3x1at+7HQ1Of3SfP0ozMirtXuYcZnrNh6Qgy3R0b
sFSKWkmsslTOF79iWmReUsBfECEavS9Kk03JC8mx5D9NBpSE+WJHaHv81cKRwtH4ufjHoY/DH8X/
WnAtbHnQGE3DgcHiYhml8cTgxVIoTXPJIY7IeZCXhiNDfhpLJP1pWDAoW6PFb0AzciIR/4ma6xgG
+JCOAUNy8KQFLGk4xPZLOkvwoZK+ElzC9ofWGDrYt6fxn6mJJqEv+XYSJ1Ea5p2ijrcc2JFfNgoK
XL0HkI5OprH1hjZMMG/B2BzLtFVnGjM5lQlG7AXttDyeUIpMEi8UqCG1UA2rvEDCtqIiUzAFCb4k
BYrEVqo5kgKTGBdKUxCw+lPMN8lV045pRhdrOsfaUGss5tBg0pM0TwdLnRZAFyOfVgL1+sjIF9J4
qCFraJ7bv/vl+prRnZ0tz059undtQs332Le5wjOefCHkCcR+sCxYe+SrXU09zfzivYfX1z7yfO+s
4R0nu44vjPhnGkm1YO7dWLvkPn/xfMX06O7adR3HNLamGLrtZClSQaELfsJDToPyDaWDdAgd/gP8
9/yGOXiOupJbGaxXN/ieJu2+brzPs8/3Mndc7AuNhSQUAkm25zhy81xGpxVzXBp81B5UnUGOD6oe
r48zuHnCdo8MBoOqY5Txxs05qMVqhXGEx1WV2bVRmIe88MBQp6FPQw3+wVALAQ01hXCIpcPNYRn3
qaBqD6FikMp9MpbzC0bhMFzTIZxoZKImN2peRQdy4p5/0eFjGqdxqtsYjxHmX5B2k6UVtbZBG24L
7oJdeFdQYPzSaMVYxQ4B1LyB35zzuNJCWvyksYGVK4Nq4DW8BOEL1WoaKoZUBLj2ZVPNDSD2fKd+
9/JvtW/fHA95IoklD23p793/zTeBJ0tfHY707klvGO6MVKyY7YvJarK/Y8fv55YYsKRhsfTuBHeU
YWFG74wg/u7YoMM7j6TvjtEYW+QbgXAzxBpErU3WPut5OIcvwSU8ZjV7EJgBWamVw4Tn0/Ac9XDY
yXGY56yEPjCHjIPAJmFc88ZpeGm4zwzmfAsZxVcRh/9CLYiXecrX8X084d/EnyALYwegrJuY0Cly
Q1OtmJyJVVd1k3is27bzzHQIxafIU8Juslvgp8PHVKmNJTyrqBAClVV2Q+RX+MOpqhY4PLW/tfRr
ZX6ytOjWaf4X3niTmZ0J0HL21ceZvrhQBCy0bEfkMvmw4HKEb+bbyU7jdnGrZZu13bE1uN/4jMMk
Gg9G8f1GEnGrETfhlDCPDGQU1iI30NcjdQZg+bOAionw5jCrTIhJujBgI6z4H3jd5UJWt5ZrHpBO
oRw5J5jD5aThCZqDojTaGeVotCnaFx2L8lEYBcoYIZ2iprdM2JRf/F96kckKxmQ2z6q1JNOM9I2M
7oxdWenWRWOGt9BotxTJYV9RqChgVVPIL3lSUGhkq6BZSYHXzoYCMZxC+glr+qTU1aVnoUtzbBXZ
XKuYFgvMcg+0hMuaZj39Nu4a+3X0hx0H33tyx9lXtj77h7M/Oo3LcmraH2r4bsP8NfFv+8J4CxT+
9Ikrpwb2n9j32u3xqfau9Xhk17LH/ritr/e3Wx+eyVD4PnN6aa6f5V4IraVeNfyOfV35WelMAbZY
vY5cWbQMuy0CRQZnmltGAwp1M08kiQFmhMq98lxJDaidKqe+680v1GwRC5Rm+Vi4WMGbZEFKyBN6
XPTQQGsMvuCVuP/jA8GjOSfWH/1fQ8j1U91VxemtW1+2hoAi6A3+6/zz7Gz5+akKDlzILeDphDXz
yGgAKlqTQFAiEdPfyjvAM+niItQsEKfAYYHg7L2IwIk4HoEwytUwY1MzwAXxfBEWIuYK8GXGn8so
iHhYSOOUQDXZTDpIJ+EJBuARoQQfIlBHmghuYtuYkhaCEQkSzMi3gvmOv9M8JAkXBbxGOCjgzUKH
gIXVhlXaceJGIzMJmTuNWmvVLX2isTXjyZ+c9LjZJGcyTNHcMZ5J2r0FIyAjX6MDcoFdET55J8X1
3n4P/xx+Uz+1aWr9I/CBxjgZIXKSbEA+FMDufqyHJQcCClb8yKf4kD8Aig87T3PjyMW6gXUTN05d
RuxTOMnoy/OjQAt0AvtIo4SNKFGtUeD9i+8nElr+s1f723VIZJu8s/vMGZn1WaVe6jXaJMkqmxQx
UKcKuZJD9tg9Xq/P7RdUZikGwnO0abB0VVKfY3F9Hohmt4NF2W2Pkt126dsDufpEX5AdSatkZg+v
lBZLi+QHlVq1QaqXVzpXKeuldXKz8rTcyXfb9kndcnfOXmVPoEfqkV+y9ygj0oj8M8+I8kvpvPyu
/7zykXRJ/lS6Kl9Vbkr/km/6byozRWmJFweYKrIgIb+i+ESbySvm+VzePCM2eI25dqc3d5siyUFZ
8fkK7LLT3mIHuyzZbGl8jtqx4sRYCfiPIpQNXBqGqMUoS1xuXp7RKBp9abhFRYn9Bx+1UXsalw7W
KqCk8XVqC1Jbne0zG2d7Jbhhn67K+R7GLbdHK3ian5TZj403WAmcrOq2Zetcd6ONZUU3c4sxN5Iz
IL/95bFb3nmmylDFLr3wxf7ToI1VPNXABEY/CJRXlFdAGWRPBTpVzZg7Mfn56oL7U1MrV+aXzYMr
IbhU2bhi8tryyuJNn1yHsx/URgIJQzgsuUuf41fffnHPchIO83H131xXDWwT5xn+fvxzZ2L77vxz
dzk79+PfxEnusHHAI+BjXRmURUSDwGCzKIIVVJiIM34CE4PuR5RMWyptgtJujLXqRCZLsI6kplEl
Km2TGJPGtIl1HRKZBBmiRKuqlFWQOPu+C6Bsifx9rz/7OyXP87zv+7zt26AfJWdv0n733Nw/3UGi
wyRE9ufZFhOayMSmeip4puXN4JvCWPAdYRHTAqMiPIq/FRmM/hAPRX+GTzXX8Dhmm3DAheJr8Bbs
NhmOTyqktblHkQLhu6CO141pr7mzMQzr6NYon7vIQa6OV40O+3/uR/46Nm0zzKIagBDmudoFHqp8
mUd8s52GabZbk2BQUiUkEZuC+qS1qZ07nIqWqwz0UC//YKDaMzVdpZWNeMbpyfLU/WkC59T0FHfV
qftaRPE0kTEpvSgdTXkUtgM0RcjCyO4O6BP9HbTaw4W1fqBagaGEU9RRJCzQqr5U9LgSWoZUQyFJ
a38hT1hw/VlVV07+4sSHRw9Ovfq9PxxWX2h8PN64cHloDJbf+/Fwm6CEmxe59zQKfxo72fjrrXrj
k1eq58Oj5x++O3MNbhxfEw0pFkW+DQDXJeI0CrDLLtvFXbFDsdetEalmjVsTRWaT3O/p9x5jjrHH
Pce9w8wwyyZVJa4bKVXJ6QnG5jjUx+iBgMoqjJcmn05PvDpCqkfxxjgFwQTJ9HgBvJXrBB0cteXo
L7be3p4j/95bceVuLBZn2BrDeGpl6tWBl/Ou92LyrEm713nWwc5ae07tMMnVvc01jdSOWwpWNvQW
+4vnirgIOE8ohPq4pmCQrpQnzkglm+jdpHOYbKaHybNLJi7DE46ZIWh3z9KFMFiZmq7cnn2Qq1Sm
up2ZjLtPcodsDSeJSD3rnu2mrYGbug+4T3Pw8Z7LkRJbIW6Q1ykfBT7hmHSdD0ejBcoaOSPDGCWr
q8jTnpYo6pRZEsEabNufWeJJpQIB4ct9jRtcdtnkN3dbK1dlDzz6yLJymtic3Gi5IsFMpJDPft2N
Zu8mOvc3sjtiiWxj1daMqJkrjzZqKZGzd+DqSy3ZVONve3ojjncskMI+SBhVwfv2Pt1hSLcpArqd
Lcr6dn5nF6MqSDckVRF0Q1YVqCdYVeH1hMAjBBlJRhRRmaHgyS56VTbYfuY4M8HgOQZaTC/zPIO3
MVeY6wxmXPRrjIMxU5/77BK9S4KGHXfEsV3rJ35gQseW3qs/r+Mr+nUdbb9J0qhSJVaJKr9SrQ50
9ziEEPzL3TkHXLqmIvMIOgDOQxih3oBUWZE6bjQ4O25tTEt+n9puWejZxRvSst+n5axUKrVYO4L3
7tJlQXLimZ84MUWolWj+HYKQBi7aCgc4qAEN2sZmtAsdQkPaGW1Eu6w1QaMOf2QXAju7+tDXWhBB
COtGdKnCrzB8qsLpCU3VgEW6Pwb/ivEciiUQZkAN7kV19FvbjIqOLkVHgqKjS9FgWZ8jTJ9z6nNA
853Vt1fmqwoBoIdzcJieplKcIjK8XSmVHDzgQI6oTcQLEHHwSHvm4XBU1+U6pe9/NFnYlIrEMj0F
9MLezRrXlP/ujp9+ezc85G28klqm7cd7jmntqRRssw/P1DaokXDnAYKKAYDnE4KKBa/ad4MSDABG
DMj+bLA12OayvMIKuMLcIu2Du6VvmIel0/A185r0oXQXfiT5/RIpZh5rtYW7pC7rixKOWhkpbWGP
5LZEEedAK3m3HHxOLElFuWiV8+vzu8ERcFA6LO+3hsBJ6fvWGXDaGgG/tM7lL+b/KF6VruRvin+X
ruenxHvSPXki/wA8FP9jpdbAteJqcyvcIm4yXxQH5d9Lv7NuSDesO9IdKxBUFVY3NFVp1o1OVcnq
BlIVRk9wqhLVE7qqZPSEKEkGdXKSDKAsSbQnr7TMsCWJlimRvkP+drFZlkXEMgwAlpXJMtZXSUbJ
ZqdB5tZz+kWdKnhC9+hn7TzMQ0Qf4eeCWpBHfcGzix1pEy6JoAmZpL7QoJsvmQ1CqNOgnRZNful8
8HQYdZwbDaT5bkD4Jm6P/ICqM4QqJhduKsP5hStJEl+SOKEEGKkk1ueuj4ol0QqXaCsB8y8yqIKK
DqkyCoWFaZQmooFwQR4t+Bji1bPTSqrXamStTcloOLBuAzEp9+FteNzcnIzGUr3m7BVrcyI6+6nr
wMzBo2pbKrVEG8AHt2bjmdSjf7ictzNDTz8YevQDknFzd+buuX9FtJWB79vrhgQoDEPS6dcXhxEU
4ghmUEdoWWgw9Cq6heaQN2QYAuHMpxuEM0U3MOU1Eaa8JgSBhwgZghEWBINk6Bt2MFODPpaFSGlm
BBY7fDQJG3he4yzO5jBXn5u4xBNySDB9yekSJBhzGsXZVtqzuHLRboVaK6QzH2oNhekjIrpuGfCK
AQ0nYw2O3jTqcx/bPnrVkLPb33iStcSWk7yldFcHcrS7ENK5yVlSzcrzXBOLPk8zEEqw5FDs5bpp
Axl45it2lhVkoRWWQUlYD54TtoGtwj7wonBEeB2OwHE4KlyDD6HwbwRpv9kCyMhUJZK4DNDc+d+0
CGVErXDUXxbqc3fHiKjsWImGbz/eFGcbk0ukstPwAzsolISoUEJchLzkUoicvb2oRB5zfX77bDRc
QjZfAk9M4OOdqgpUMBHVkv+pxYn/V5nT5BTYj1dQxcAPqJaSM99R0uuJsKiQlq9YHl/u/tKMFwee
SOXRSdcXZt57KpwLz7aHWDKhrCHOcJA4wyaggF/bi08L570jvhHOdQge9p6AL3tdzzD+LMCRrIeV
ulVsYgQwhzVsYRu78do45be5XNTidhzF+W6O1Vg0P6yujT02c9TL9XDV3AMagDIZUR3rlodKMLUo
3ZwOpQNNfAdQoNQBw14SRd0k4nz+DigjsghMpAOILrIsBCv3Eklg0ll4Duh0XdolErB4jvo3gecy
/+W76mObOO/w+3v9cTaO7YsTf559Z/vOd2dffL7EdsCGJleh8bHQJkwRDVFCqJgoFbQJIbACQ6Qj
rYFWHfRjMP4oVFCWiky04StlaEk/qNZ9qOyjGi2TYNI0rWozWglp2kecvXcO2oem/eH3fe/1+eR7
n+f3PM9PxLPggAPVPdXPq3+qHvjd9F8uP3nohScuTP/10JMktw1Wf1P9WXULvADLYPnP31pdGa9e
q168cBAy8CD0nTtodG9Esa2K6fRN8NTbSCWv+lK5mFN3hkaYkei35SH1lSi1O3RFuCrfYm5FPxXs
YYlWZbGUKklLZU3tlR6XhtRR1fUBgkg0He2I/jZ8i7GNy/BT4ZPgp8In0k35c8Ee1fmY7PAYUpoE
jqESPBFaf4JHsXhTJia385085nnKn5EDAT92UA4fitARLaJHhiK2yGrVgKCtvYhU0NU3VXxSnVFv
qBa1CUyDBNMKwTRISHo9ZrV5zE2P6Y+eV7PqFHzrQuJRApfycM0l52peadZb/0PLSTGIluxnjDnN
rjdTBD1bbzSjs75SyVdzUAJqVEgHo6GULKaDYh6EKBmkcCYPKYbP34/iTz+NVnfv1mmWyA+/1Jpk
40sJhBwCQ7RJEZg5ffswDBvlqPwPhTVKo4WcRaOdT4pSwMjwxYIR6Sk4ExUfKsz9iPhzI0P8Gb66
/Ksjt37SPPxg8RuxLcdWjXXnu/De6s5RjvjzEm7Ess1YdUzuOXvDs3LRotdGe451NBDkeYRsWwjy
MipgrE8KIeO4UuahVZLge0a8zl/PWlYLP8jiEBdUNwsWJzhTYmol6oFBPCjshb14B7cjviv5VOow
VOLHs+fgXOqKeC07L/jt8TF4XhiTTgivwxl8Vjifnc7e1O5m57NuHwpABPtkgm5zWS1rm4XHc4sy
DhyNgp9jvIkkSskMIvHSk+ADHBNN8DpuSglCEgNpe0GYwHFMZdKvm61C0Pi7JO53URspyxHqFIUp
xExEC1NwVPe2yLFYFHs9HgDk8CXI/ZM9RWPSv9ZZRInzCdxJzBgnLtGtoLcOtd5otbQWHCajHOY5
OExGOZIBv8kov7npNxnlf7X46NsQRv8KXQvNwPC9/u2KYrApV2NTboFNC6Y9O0sTOvUP55Q5shGO
0LMVD7FtouvgK0UIO2nS/M0oFdq27/1mLWTwLdvM8lwqy+fy0MySQU025REvaPGWPCCF8Alqrd9w
rfczdT01f2eyrgTEayYbSzKxr8uNplCT5ZeX6JJGe4k0Q02Ric0rSiIBJtX+HxUpCASC0LJARsJF
25bq96rFfNzN0lFxTdEkpRka4c83f/Hd0+cgtPHw4D8eaIg6371+8kB5E96DAaq7/pOa7W/s3Dcl
Vvc+21OHX4bx7+w/2WAk7NH531ttRLWX4Ef0sO+VJvCCF7ssyGuVUdqmdEIndtaXp2CFfqN1SWvE
wlgHQgPhgcgAY7e5bR6UmSlbR1wj7hHPLu8QO8QN5Ya0Q45nXRV3xTPmrSjj1vE87XPn3QV3MZaP
FWJFEt1w1hpn41w6nc23QRtut2phjdU4LfFA4YHiKveqTLdrnfsRel16nRLjgMNMnisyrd2h7nB3
ZH1LX76v0Ffsa+1d7LG4XOkGF5PmXfHy0rRWHvYNNxwSjlPHc9/XxnMz8juZD5SZ8pflxocdSxg0
iJnz8BFg2A8AV9GUpUN3F080R5nYIMew7NWYsVMIn2jMEI7VeRrr6jxKXcZjFZ3mZOdhjiRvudnC
y41OPAE6mywAcCKIU8DrdK5+uh7frod4/fn62/WW+ilcucJNsApNKtq4gTupwrR6V50nkqqvLOrq
R+TCgtS4qhGhtarXYAUqwQoI1eje369sJzY3fG92jojn3HApp9Q8z9RLI5KSgbBa8RhZFNFf3COU
niXdiLHqB3o7WZtK2ipoVIMsupqceZT2GmLaQAZKI5eLsnV55KprUiSaSKvXk86kfEReHTm7wXnF
lFFzqHklYT/hfj8JQs5Nrs3ux+hNirV/fT8QbUfbkZl+61whb8mqeUt5zWvGkvVQz6uYT9r9RiPI
YlNrjWybtFN8fZ7FNZpLoiCKxUJrvsWw3dbFlnMpX/9E35aDSttnP36u4+61pQXuvUg4RqVSkZ5L
2/YdXVyWqmdeWnPnh9t2LwlGEouIEyuVUxv2r23Ld+zb/MTLa0/cdtra2Rz88sWjG8d6WzY3se+N
PN/94q+LYS5nML+NePKbpid/pZd7oRf3xnrZrbAVb41tZR25RHuiM3HcdowZt51lKAwxNmD0kkmn
oZ48FeIRh2mvIzGFZ/QGJyhID3rafV7yuC50HlnRFJb1iMNp6pzTlDSnqXPOZDDAKayhjx7jF4il
2QH2FGtlr2IZBea/0F2GCgZM/QuQp1+If5M0nTQJq/f6DcFjicC6isYDJl3eAjlg5Q/0sloraiKD
dFeRfO5/9UfTYueWEcukP6Q/NLoV4oYNvGhgwP+XDhkpkcDSYH3NK7oauMe6p0kSzM29Y8TC0wNy
4euUSNvWVN/tFsqL/37vfgS01nkatvVBm3GqRFRsb5BTVeHjizYEPs140XES27UNoQ3hLs3aFNwb
3C3ulp4LHpLsYVvYjpHmp/xyXOvSbDabnbLLfmxNoDgIlCwJckrVtBWga2uhh+ple+QubYd9B7VD
3pEZ0kZh1D5GjcmjmVHtZOY0nMantPdjH8fuaPFn7BWqIluAwgzUgOPEOMMhWWVQDUI2FGNYQQwF
g4SOjZIkUg6H0U4kJZlcySExmJMpzSFTkhiycTQgxHGsAXkwMDX/t4sGroH7fYqx0L0mYkndQXKr
ATfZu2IiPhGXjFPwuYtxSZN0qUsakkalIxIlTeHjF3JbD4eUMKl3JUJQXBYJmViihX5k2UKpl0rG
p2KtlTuZQ+aCuBkpfdPLzPHf12/Z8fLunotlsSxh1L9+oU81ChWGQTH9yzZ/559cV39sE9cdf++d
7872nZPzjzgX+2zfxTmTYCdOsJ3kElNfm1AIAZIBCbDNxesYaExdk6ChdVNXd0ARZW0zVdukiaq0
YlW1TiPQkIbRadnGxn5FYog/mDRoVGVT1y0Tk6BiapPs+97RrVqie997z+/dfd+9z/fz/XztGihI
cHNAKiHaqLQQkS3RMeD3e+dkFseYxXKZlaOAkf8XU5hVEqzQoJGOsSOkuKv4T5HIvu3FlYtaansG
SlJA0sq3HspuDqVIfzw7tB5HsbcY6+zkt5hto59bXl750cewwg+S7n3rkl7TzGSaHlkZxK8+0qZl
GijKXl85SCqQtUT0tK3aHoxED+fiUxxRRCEFqPPU10c4GiF2gZkeaqp2sqtAK44xrsq5qtwkR05z
mDvOC1MYD5MKIaTBDUzd8aZx7dNMwDrF4h2qXaG74Qv9NJi2LrN4YmdCvyk2/EYdXKSysgnPrtzC
jSsHRTz071Pg5+DKFwnH/DxqN9me0x5S8WDwVBBTGCm8K0W4QAnSA7iLMZkSeMdZauw4OMvr/Bhf
5V1VfpInp3nMH28HciEI/HwbdyAD7QRYMlfLWx03wbNtCvW0/AlXHU/Hy0FwswDXIPi5Cfy8xX/p
3sqQsA+eOLC6xJ3gzqJ1aD03cI5Q5Nh6yab4LdkU63VRsc10SxJVr3TURHIOVI4tBQJkJBemU6B/
a5qSV46GQx0Nghybm7NEZsVWVmLoHljSlkNxV0umPS/bHniobMditPXDT/Ls6nU7TifJsuspFats
VGUzVMWMi8WMC2UhE15Op8tQOdDUNJ9dpgdyPT2Ps9Bh6Wpu7mY6fVm5Pt/Rnk5H7ccl7dkcCezo
xAE9YVVLr3tmvFwgHXgSPZl7Bp2UThaEWCDco5SqJZdH28JvETboGxq39NilEzG3t0bUUeMAHvQO
SAOFwa6+noH1u6QD0jHPUe9RqXZn+EiYJEp7S6TizqF8sa2lNX8JR5GM5NW5GY8lN0uWzCrcnoIi
D8vEhqYiczozh2WXXITIu2G3SNaQuld9XOWy6lMqUb8BxEN33F60iwS2PdZabSWtBfhus9zDtt8l
tc214taKiXI+Wc7n4cN/BCcgjOQu4QOoCfQpvLHGQmbCrJqTpss2b5ukamJToZPMS6QPoFkHmEtY
dbP4gB2PZq0O0a6xdND6VZFTRHxbxMMiFvse6PuyI0vGJybSW0FbpJXlNIUc5B5GVPD/QRl4687y
YllZGi8tTYBuSfstJ3qyDhud52QMXEQLPid+QJ9sLPRqST7Y1d3ZTQSP2+smgtGoNxKhIFk68seC
GgoEaxM+DTcme3lLQ93uvI4LeSmgKRquaYSmRyhqiFUGVKow0ZJOr1279mmq1zFwHkgU0Ce7z5cC
uEyFOJoA/pvugJ0CIhfOK8zM1FhdOuzd4T4wC7YkWaouWfVwaRTtEcnywlF2NVPrBesF6wHrYST5
yb89sE8T0hnI/UK+q7OzyxHzQl19yBljWqc+XOcP0cKzq7OrzikNYA1QKAyRjc81da7f+/V4y+//
sWtHyUyRbMrMTr38tW29WsBbX6vIdcWx/R09+HuZof7R7i1HH/M3fPNgX0f/V0ebTuxvbMz0tK3L
t45OtiQeSh9b+e2R3pDoK3Z/t/9FXC42ZCrWpr0IkdUPVxe5i/zzKIya8DUn8s/FeRrBCo1lPiQj
1UujVwUA/5XlPZnCjA6xGxrnMp3vo/NlWa1HLuIJznLv2v6Q7YFpoToUNT2SsQfqRqpgSzfTjoRl
cXozPaf8GoK2oz3qgMSGpIw4eASso2vo2jjPp0ykAo0IIyqh6KXu3Jumfbj551t0SJZTpp8RAgT+
HL2bv/++efo6eIH9hJLCZ4QZ4YL4fgIyRp+v3KmnvsIddj3DHXe9xr3hFjeKuMcdWuN7MBgP9av1
MnJFw0gx8H896UhQNq4AL5/lOf7vchgouEmWFd+wb8w36XNVoZnyccin+HRfO9zO+a76RB9E/1vF
gq9i/mLQKWchMFh+gcBZLk842n6i5K+37i59hO+y0Ghu0DlJTOlcXMcRr6qhBlWSNTf0Ei5Dxw1S
VEMxIaojJ0MzqU5lOgAeMA55fs8eDDCDqlJ0sEVzcqO4xsz5/eH/FZgC7j32/eeuvXryjeEfjNbq
qra2Bgdbc49Zn3nppX2FQjP54OK//njnO9WeHu7CqU0RJTm23Lz853W53/xs6qfREOS5hwFDmyF7
GPjuebcLf5w/SESQKSYEpn8FlgOEsFnrESvGmEEM+CQXKJ6MGDD+dDBERuDmdzM0o8Q6OKB4oO90
uXR5iQFl/jJFSCBJafTQ2tY8StLTq/ft4okW3Onawe8Qdoq7o7s18QB/mK+iqjEd/ZV+VV9Af+E9
XXgjHlVHtL3JilrRDqsT2rOB54OT/kn1NXyGnE2+iX+Or4hXGv7mXtTe1+9gVSCbA7sCJxMn9Wry
dlL06/jt1QWkw5UAwkAxRAm4HXBRMaoGQYZi6MawQfc1aZw2pow546qxYNw2fMb+2Du1uPZK2PSI
sL0b50MWNXZ3wIJNSsYfEjIekl+QiZxVUDuyUQWNoUk0hebQAvLQAYJ+eChyJEKGI/jlCI7MYtkO
3BYwEhRBF9oFW+CFvsa+i+TbTuE4Mb51qTwxvjxeXhxnsEqnS0tL44y6FwP3Q8y7I/b52KEY92IM
+Hh8D8RGd3c37gaRQGGDgLIpQSJFtaLAezNBi1cUC1N5olBmnDunOISH0wCxcSwAvEghjxjWnAJv
jcN2IYfbuM3mjSOn3sN4+viPOzK9cb+UTD6wb/2nXjnx6LauPP7shV9i4Z0buOaFralsqu5wIr75
0VfOfNjX9gTsvn910cUDQyVQKxm8j61U1qbIahFUBiq3AzAGNqTHwoywwpJOaclP8aTLFGg6mw2j
92wGSV2lK3TtJ9y7KEYTNfRiiQClLiVoe2rISDCETDi4TIZjioMyVxYufF9h3AR9McfACRrjY/ra
HoBVSJc4ji7VxmLYjlViJJaQ4DFSmHFY2EUJCzwMUau7amuhJfQXXf8P1dUf28R1x9+7s+/OP3I+
n33nGDv2ueQcJ2fHTmMHHAI+SEioIUoKAQKem6hU6yp1IrFK1aFWZKMMhVZKhFTaVCphW9du7A+y
EIZBask0Sgtr1GibGGWiMAl10pinbENoUpWy73tOh+rk7vveu/fu/bjv9/P5fJPNjbQP3Ry3k+OS
zRTVFowquBnzC4ZB4OJWsbiQqwCyAcBBbFxAyYfzZ3t60kkSIpuM5vRw8mXLy9ZjlrHkmeR8kjeT
Y0kGJdUmxdhp3SkMGCd4fguPteQae499l/0ty/tNp5L8fHLJYDQNaZGL4O0OYMHNHVqf9pT2Xfvz
2kFtGk1rp/kL/JUmR1TwNDg3yiFPl1LXoG4Mhuq6wjDMYYkr9NTCcRyPh1lHGDkiTo0IDFkZVsfU
MyobVidVRr3X2M/BWs/GmtPEnu/JcJ3NnYeq+AgqY7lUBP1KfqBmARwrBB4lio9IegSTq6KGRWjQ
o0KjhgwL3GK8ruEma5wCI65CYnEt8XDw71FcGi0CPwM7V4lYBiLOPELGKh37rKsz7mbm/z7MfNw5
lj9x57+/+0EfIOQqowa7E66IGkg4vl5q5jr2JQc3F2aeLzzbvf6rjz7CPb2/fIcC5Ve3ftITdK8e
vYpvdI1k+773ybU/g0dvA7zcwc4gL6pjX1nx6JigAt85XeCCSKRGpIApKikTYQ2ggUFIghscFMVK
UjDdbjeUkCOgu3nESzzDk8dkNE/RFfrxlvLD63QEFK6dJ9FgaXE4KDAQBQ0eRLyqWCxStwY6Ti7M
PyLjOmUMnQI4YjWKTmx1EdUZBTKJWU9cWOI1foZnET8MwvEUb+GPW35qmbWwZCoetkYiMUrc2esN
h2CfpAi7BbcnuwUDeSg0iWI49G0KNxYWCYsXLxeLxuN0rbBS4u6mXx6qLfqH0bD3Omv1a0GQacGs
agazYbIqe2c+LYQJRYSpi8XStHlHU3M6wPltg56n1CHf3trCKh6zNo63CU6r8gQ3zrzOHXUek47U
/Yz5Ve05z5+Yz103pfvMf1iPPMwPCyOwu3Hbb/lPXEs8MB1f8yrD2kiccBAn+TZbN9Nj6wsPMAO2
p5kSM+4Z90953rW9ay8L52wz9o+ZvzF3nPftXmGRh6R1kWdGiSVnNwmHNsNz/CsWL0qpClmqR87K
Q8ohZVq5rVgUJfBHC4YvuAgEYiES1UPMDXOLnCVn/J0AJl+E/1RQY4GsS8X71UPqhMqq973eMQGn
hEmBSQkTwm2BlQRTgJ0IM8IdgRNOi4oFjRO/YuOmnBJNsV9kkSiJmsguiVgkK7HBWYqdoc4V5QIp
QO/yKJEto0UwFdD5EiGaEnEpo+SGTwRae78CWpskpMA8QD0kBS2itWvRaBF3Ds5xCDPM6B6aHJAf
VeQXEA+zOVZnnWYiWwOXQBgnluWrhmDEbKBaC1SfrdTs1Zq9WrPRminasorkz/o1d7YGLgoF31Lp
e/bs8XA+ooPW+FYYTCYMpkeAvQAOuJv4mWeO7j2SCCvX3vr5vX/95u0ry0fxL6ySf1/bjsPMuk9f
eGHfS97xv2L8+T3M//50+2D9WvOHoIf6EGIPWl9HBiOsRLeeoHyVMAntJEwS2AEDSyKHBbERC6SO
ZTjrv5syCVBRpqFPSUrkCD3ZgJPsQr0e8iHkanSVcWBW5gSUzFXmpfncQkWqVElpnsjpy9IV8neZ
JL7f0NIF5KJjEAw16xq5eniT0IhpIGKORCCmupou44bpoNFI26F+k+prUUzEv6GgW+QG0y8sEN1K
wnHDa9qUMhVlu9gu5xb/EfaI0/q2BScThyKT3CQ/LUzbTkon3TMJm8QBTg01DRlMUBDnQsLxx/Bc
iC+zghleHZoOXQoxIXe97sNGv4SlVFOj7OYE3i6Bg5fx9rMTkPCWmQezuMkoY8msiTVi2eWWjrtc
uJ4469nh4TS17e1Vm8tVbX0LtaYajKQnRUxcfEgcEefFRZET/fGLLMfyVQVVrDplbwVcl2a2HWC+
LN4tAQvlgIyWSx25Zchs4SAo/8h6g1eN6kpUV2NB1OCtD+IV1iFUg+ACkeT2gqe1KpEMuFtbxr06
0wopIM0BqWKqCibI/JRWBb8X1DfsWL7VGNvkn50dPDf63GB7OuRrzYfD0WYz+A922/J7Y4/F6+tj
XU8ze7d0jH94oCuxNpSJfN/jaXn2+qYt4H5o/dfd7F9Ak69DT6A97Jvmj2S1/83oVBuLElKBebHp
xR0MauKaue2vaZbcmr7C/jUHoiOFCcuE9bDv1dqJzLENhzdPbP1x3xu+N2qn+sqWC9Y531zt1fTV
rfOFxcKdwlIhsEpTWqWMty1csL4v5NtyAaSybZF8APk7ZbfkEmucDrvN5vF4bcKYjmW9/PCLORl4
SCefw+vMEWs6ZEduWj+jX9JZvYxPnhs0xiDZgq5mDekrT0fORC5F2MjKGGphSAT6mrWTeZw3oTVv
QlM+TkIn3+/F3jIWTM9+AR8SoOCG1wgZbqoTd5bZFtPpz9uTftzvH/Mz/g+YPyAOgqsXdcAjO8f7
n8RPxuOu3g/ZFPBdCO5Z1MumzLCUwvtTE6npFJuqJfyacpKQSGWyzezYAB4ge6uBaIXCtTnJSwtf
zJEuUFgy7TUQSAN6OIZj1Ad9q9ITMdwXG4nNxxZjlphIesKj+3Mk5KHwT1MmgBE7oBVSBbNwCs7c
WiBDgw5nuiBOnOjG3RIZ1N2iqdiljqifAdiXH/7bdJNxqpMIA5WuUS0zH5ieqRzOtaTYfpbpZzFi
JZZhyVH669LUwltZMj2RyaRwnuyRfW5v4SJ+CfI6+6/Haw3jAQkLwPJKaZkWKkbprmSMPqAVo0TQ
3xiV7oJ2g4RWqqyQwvKXhCJyUqVEst4iGNIfOgNLzH0WuR1hgCdK9ysgygzSot/WoaVEAs8N4hYQ
h1yYWPinEXdw6+72zfWZYJ2vFluj+uMtrS3pFpbbGO2LNutN0V36QBAH14WCaGumV0ObcE5D6625
IOpP9AbRdmNAw1213UG8s2F3EO/aXdcegO6BdWhbS17DW/OZNpPp1P7HddXHNnGe8XvP9jm+nH3v
2SG+cxzfXXyxYx8+h+CvA9NcIFAKJU0LIdAtkJZuk7pp+ZD2IfbRdNPE/piKt6qbBNWINK2qtn8o
zSBom5ahCO2PhbF/0P5YJdZNaFWJhjaKpg7Cnue1TVGd+L3nnvc+/N79fs/v90Adf8JfT5Kx4rNJ
7mDuWYPbHd+V5JiC0LqNP689MLY/+uSB+Pgh81ModnNM2jzRoYDRMo26DgDinSjrn46SDBhQrAKg
O1gJgqBD6VYPJaDzjLM/NoNtVbkEzVSlys4ifXAAk69yKZshwuN7sF8+9Pza4nenr9gRnxDwyfbX
aqs/H31ys24OJmev7ZiaefnN//3+e/s7lXLweMl2yaZ9L42Wxp9+cffWjf8WB7e99NulX24tnfkb
Gcu9fvT7q15ACMUTYkDYO7twsSvjdilG0O8LhMKzz82d+NHkUEVV+3eGTuhb9PQx/tRXT/50cuf8
yXPP77z/6tYj/YPWE6/sLXV3+0H0uTAUp/9AN1fhT7e0sbfmIXGpqIhMCEXVwn01gTsqNGuMExDc
9FiHp0YQpGoG1VLHRMYslbMFYvoliZ8w2TXMgorXKCw//HgJsxDcW8KJQptjENz2ZCbK7HoFAl3Y
iAhSG4VvP3wH4JvlSiC8ctkLwbnlCpdVejf7gwDrYhF7QVDd27cBlK1+kJlWunp1iK7azcwaNIir
j/WGR0pRpGSZjXDHbAkuipdUsiKTX5FJrshkWVRZSmUplaVUtVYlJkubLG2ytAmrucOqDQT/XsIJ
CO5fwrlCoVZtqTYT7Va8hqYLVgFt5JrCeAUg7vGKNS9fFmvT4JvlfjmzUGvU/OdrK7XrNZ8tkPHa
dG0WU16NGB1qLqUs+2RP6SvkUtl9fWIuRfelzVwqs+yLeE66nHVGSqnyKDGyFY6tEmyVolBRU61Q
QyTnRSKLs+I58U+iX8Qi1V/gTMvRC+OF6cJswb9QaBT48wUCilVYKVwv+AvT1begO6T30FCis3zQ
3IIuIxNhLXXFdVljiA+flYquRDLQIfT3ZJIBLUmCHYlgL8ozkJYJ9Nw8N0WgeNko0ajHSEPU6u6W
VldBrFlzKARZawjZoWqlnYSOkRyY+c7I2GxPLCIOehtPbPKGRJ8+Orjl5X2b3D0b23aku1RZT2wq
Rkg08NqDF0/uPvxZ7xcbv5k01KRlZTN0jIz++Fix9MxG8pijW1ZMrB327Wh2jxzY8joMQeBLJ9fH
P9VkzGXOAiHoRThHwwzuYVNFJJsqItuMqb4QKAir5RDcZMAPYReI0xBcu4hHh8Jqu+JD8P5Si243
23S78SvGNmMZGBB/xpwxXwEZ7psBDk8LRGBOFh35JbyA0CfEwA3egKK+NkXfa7aSALLmCJSAmmmv
IsbaTAgbjAMmG/E6S/v3t4KRkWbgadWqMOEJhBMWBR5vynGG2ReM4fLueUk8MxSy0mHGhzCPsA8z
PuDKmnxQkfiMP5C51KSQlX6MA80eE377e2vDa1OsH2lRQWtYZNqatRrWonXHChjWuMV7OFgomEND
JbatbWtuC4PNbbqfbT1HS5SAILF9feFcKgq0yGojRsoclTQp1oCluBzXJwVjUbERIiEXNfjCrjJu
PHm47PuiJIW1sKV6tqtiLlHZVmqoZFwl0+qs2lAX1TtqQL2QvvAzRgf82evIAZDe9aZNBeWFpdEW
GdiS4ANQnyLzgPWhlu0EHYk9wjWDdbaN61x++/Z8vr7929qWkY1du5yeUDCVSA5ESFfgNZyo5/Pb
N8wHxmEXgJyoT5AX3thsaLI1y/EPT2zsIacDpwG1ObLaqvOdAzHWBMV0fH93l7BAs6AFz5tteP7F
izXx2cS2iOmwvvxwg50CwW12CgR/ZafoeEoIT9E5IZdFvEoDkAD7lOvuuUa54vpaEav1jbUWLG27
DUz7KvQuF99MEEEjNj7p4Wo5bF+A8ufZ43bDfjvydu+iLRiws2D7KGSu275Ex0DWGMmmBkY1XJIw
EUuE8lqPkZOC3csk4oUpx0lBuLN8LkZiy+QLXj3ffM3ek2WfY8fjCXi/TdT6GWo7GGotXW8YRDbI
tLFo3DF8hoGHGMsPP4KOEQ4wLuTtP5v4zu2xu8yJ1Q9QtGL1Mbr7c6O3DtyFtw9mC/RpeLjJs/PC
Ws8Sw9v6/FEKBdJVmJWK2i7HsMGKJE2mInJvf1LWkyQV6UGXQ9r9C8gENDCfAkwrwvale+uncDNg
1+s2wGPhD4ufObLFTPQoL5iq0/0Jek6z6bxd3zDuf/7Df+xMp4fCwcn+yR/yP/iJbTIEEU7hOL8E
da/q+10LP3aCyb/GRkNCCChsJGyEDCKgG0fwBv9kGMHAs5smoZJ1dNKyB35WKAVmGBym/043gstp
+wSn7RMcrKR4AQg2PMpSlCi6PyPGE/0D7EZo2X8NbiHDlQF70QpzC5Uql9Ek9tMkgOTFkBRm8Pa9
/44owBuy1+2WiXhgr6ysoNV9zEbYK1ehagI+gbpck7pYky7Lru7yUYES+H899IbY6GxIZ+Uzytno
Gf2c+64oupqbOE6PK8f1L9EZZUY/y4c+TK3r/ELo1chV31X5A/4DeV35V7RjWBlWh/WaMezukefF
r8gdRT5PjX4jU3RrpEaDm+gEeY4eMvxpOkkm5Vv0Ixp4StmrXwldEf8uBuKhbqr36vpufqcsdCpy
LJyQeuVURBcO+ib8BwNH6SHlUEzQ5N7elH6Q97fKfrGiMkwT6hOzZXhG35SI9A3ghihoWUmCW7fc
jcTcDTz0W6yOo2lmdRyCj1kddxy39omvYbYG/cwaCBCzNHFmaXq8CSoTXonGYlTTEynNAauS7RP5
UEpEp5JNV7LFkXKqMsoVuU6oO5ahdxmEN3TwhoOE7yKEJwZn6DHiz/KySKkqVjkuvkxue0+r0h87
O0UBkK9pqtg5KC1I/B2JXJduSvystCLxUjEeP6cSNaG7xAVrw1nFIudQ57yz4lx3AuMOWXAaDu9M
19xl8vV3zbe+zKg9Nz8FxAZ3OUbn72F4dwoczyObU8ep4bqGS8amCIBD6/VTEUe1I9+iq6c6WgEH
B6gtBaDrhK40x1M4txoMHoXnMz8/NzfFTc2TKfbh5rg5aFYucxRo0wX9ij4AnRd8ez0A3oDs8qhT
nW4nbpT/s129sU2cZ/ze8+V8sS/+E9t3jh3bF/sc5+KQ2E4uJiRtzgQSSOySAg4xUrpsisQmNi1M
AjqggCpV07YKpfuyD5MK+1Dt00SooEursUXdhlZpFUjbNLEPfKrUQqGrpkprN3D2PM/lQtBm+d57
7nnf9/Gd7/f8nt8z4rdPrfZJhtM1YBcEqwPZBgPqCGLPYg5158yuiCi63SHqabDiDGOzwrD+qLau
Km8XVgfuT8tSVze7dPA7lU8//Ua6oHc835zojvc0P+7orzX7JzMRr9+nxSK9QRZoufR4+a972mU5
nOA1je8fvdv829muAZ9H11kkpA6yY807jZ1RputBr9r1omv35al4MINM8xwoLD8wTYS94egrFeQF
6auwLDI3I85gxBmMOIPJKLORNsB4QB2G7EgoGYUWEgYY927gHrnlJpCDBIebCwFBeENhYohwBBxI
ASVsJJjTMeSxZwjc2tY15EKkksJhqjWwjePcjIQOo2RhVETwpmzRI9vkRYYtemRZVZ4R/uOQI7bO
+dWKuq5+rrpUVC/jk0N4tnaNjA4x9e22peFZlVnqrLqoLqsr6hVY6JaNpHs6zYykmMuEc22VUDK8
B27JLXo4prfJm2Fkki3m6NCKzGZltigvyyvyFflzuUV+W9kmW2z5Pj72VKgssBMM2Y50yrPaxEHG
2Y6hqeb4eH/Ml4rGeoIs2HLpP5W5nQnSIS7rZ1O2eqYqIhZcV7kjrj9vVhG1Qd1mw8J3pQbp1Qbr
1YLD9wV8ofj60GP58R0X8rQqXyxPOqsmnVXosbpw1WRlqkLrKgSUCgGlUg3jr1WdfVWnvlSdAGD8
2+rAtVUPhqnmaXuetufL8AItLzrKAdwG13+xvLiv3ImB4fqBlcKlZZ7meYxRDlKMIMUIalgDKYZW
oEK5tvG+HUPrxRhw/XfLi0s1fnP+MWAU4mhKx0Bp7z4UVNrU4bqFawbq7ED9u/ULdVd9TpwqRrN9
XvdYX4sbNcejAaxoCwsgrJ6s48cpaFuK6xlzE+owAt7zdL5FXUJ+C/ljEB6ie90t7sP1OXe0OBUk
xAc1gcpIXkSY58mXL1foqkJXlSo8xwMCv6bNw//0JaUGGbgKjH/SbLk8X8Uaj86qk0FgfEmz1Wpj
fjNxgltjAO6cDngEjp75w/FxJGVA72rbzOH533KTG59we+EYgKOw8cmNWLQjGo3utD+NuNU55L7T
+IfiuggQbyyC3My3sZUG0yTNSEbX+MfX02UjWQTD8qarRnJqOh00kuqay3c9kzeShTVX2/VMxUhO
gmE9n6nnapXDyfoeySjXrBGjR+Lc2am5I/hisn2yx+sWhRb31GSxEFU9DVCfgaDeVdDYsraq8doa
My1/2ejP6zsLZbZcXi3zZfQptSMVvVpN1WZr/MXaSo3naoEaX4O8fiesDNUW5xtr/FGoWReia2zp
NZKkm4oU+hAwnnxkn8ZeQG0KSY6fcfrWqICR5IE/l9vM/Tz1XiBHw2ld9rdlM9263NXJfP60L9sJ
lBAYy9uilFvIM9CkDQb1AjSootqjEgmGVZsuBp1akgPGgJKjPuWRLbdbdP//zmeQzS617/jm4Ny5
yLFLM/tPdCltnuHnmmOh0S7VI8Rzc+bxKs9Hdk02i9URb0tX34Fh89COjuJMc3S8FCOdm/OzcJ5/
uOTv7l362sszM/Vd55qn5jQlpetqIBOcZT9a7rfMfd58c+alfnBCVToIvqKV6Cs3I0eH47oeH62z
l37a5+hhmeNc/wImG+S3mMwkJiuQHi7S6JP8SgYpoR+vMgndkIiSJOIDifhAUnTcpsRwQpExzxWH
nsC4R6wExmdWNy5XuARtTlCgBIVIGFEMYZBwNhyBbNgSjQyb5AzkNg/uMLhOXi8gkbQWqTMrltp+
AwUxAEcajizO6H695I718cQlAwNQEx8+DIBABog8K4238UcACQQHZI0t2nhpQMEsxr9GrBfJphso
2vH9ukTVUyKmkIg1JIVHl0IuRUKXophDXIJWJsiRoMkEPSh6DYcuDCQTXGEY5tBTUWqr0q2aOwCP
hcp0hJQpyvldptVrSibmf8GcNRfNZXPFbNkhMIvsi3C1aoqr5h2TXzXZIjjWTVdCUoykf83lt4Jp
w0jq02nJSPqmMwkjmQGCsPozxVxvpZAs7unkMqVBemI9k/H7fR5V0d0rEluVmF9ali5LtyVBWuNv
WnFjMKH3poxZY9FYNoSLxoqxarg4I2DwBtbxVkh4Y3EIUh3KNmU55PgT++yoUkzokZGtVKZEbo92
uEQh2+FSO1mLGG2JOWkMWbxwAr7cAgMNgJn8Pwm8qQUhI7c7n4qAQTbz85/MfFtTfN7i7uZoyBr0
CJXa6VNeHyZieLLoTzl5+Oj9mbmxc83vH0l1dOp6rtt/gJ1+5cSrzcSCkoBMm1pih9/aF8M844G0
P3K9C3nm5xK8vJlpnSADSdHJJOfsni7g9cIYEzB3cBINK4ROgZYJalbyBrKcXRkJvx8ScEF3OTht
xXlcF8PNccRUTAgT4sJygBRcgOSbQDoATUFIynIqicCiUoTgglpEPwKBrb3tFyPsF8o7yh/YB62/
T9xtFds/9rB9rXuVI5HX2OutP/TfjbtTVskUUhMAu8spdivyQYy3Umy/5NxNu4AvPQ/6/wBAUWB3
cJwVFoVlYUVYFUThoWzBpCVfhhZnIjkxE82/EPjie/naowXUdDOrPYdmVmdfPHpNTu6/lhL2Hzw6
f5OTN9Y5AY7UxjqWwIn5X3MxV4kTuLCrdD9wP77tEqpDY/OBAETDLNGe9XXz2c5uT1bsDvrDGpdg
MY0prWBF3WCF2gIai7tgiHhVjetogcFuQLY+UDYY6k1AHZuYt4In+ZPiGc8Z35n2l5WT0ZOd0kID
GiFofqzWzkBwJA5HBP70a94RjNQAiJYAn2FRzKRz3ebQ8LCaFsVIuB0xCZWD5+6cP37q9oXbZ469
8qdD5vHdl1/9+vlvTbmuvvmDq2cfX3zrx788/9Xpyvib5/7YvHfld1+8vghNx8ZXzWnXe4C1HDfC
pzexZoxayKolTy+ePCJCyRMNdXCaywgRB4c0hcQZkOt1R68R72oIojYSdq6efLvgE2PvAbeq2HKA
/OjP+oYbojtHLMwRC3MM0AkMC8rtEREuleQBm2jX1wO3gFgHCLEOtb7LlTYe30AgljyIySiaHs/o
Lrg7wm2IODKk2TVAxJv6zIqTWNNgVc9/+a7+2LitOu5n3w+ffXf22ffD9l3u7NwP3w/nLsklKW5L
47H+WNtt2QSiDes1WdsBK2VNUtBWTV1vaOooIBroJAiRyIQEQkOiJaL0BqrWoRMMddkiKEX8UbY/
oqoVOzZQmWBTEr7v3V1XhEQk+73ze37vG/vjzw9P0KSQGoRieFwNLgC/6VGxzYyozZhAnstt8lwq
YVQ/w23CaLXFneIj4umQ65SFNlmjm3Zbj1iHQ4etY+zx0HHrOfaH3lvsv32B/k17q+NDR4ZcziZU
YZl8QZLBVqmnemUwV2aaMo0xM0ltpaVSnnGVxRGEK6G9uCZVCQ4OpLhZjp7k6tw5juH+qtNyA33O
iev6Q8aUQdcNRBmicd64bCwbbmNy4693d8LMZpGw4kwLB5oW/FszoZgtdhiRCYrY/xBE65Vhb4DN
DuX8uf7ssHdQR5UAnKq+ER0N8GWdou5AF4hyeqZGTdcAgky2GsFOB+PQS3Bodg1MNbrho4DkbhMm
WKDhjtGhkZbbcWbsa/umvzr10q6R/GDM3r2mqxtMOSKmk0oWDfmCX/zkoS0P73P29lcyjD1z7fij
R5672po/GRH61m7tryazWRTlBw4xB8b7leDJtZeOpjfuffCzL/9++kFFwkkrAIC+CFjOowsdJOeL
BMmeVCxkEgthKinUCVx355NU132kur4hhTETwkBOkfiUIkYjRXIJmYhERomqvwJwK1QO4BwcM4+a
J03GzHsVPwOQWsI5pAUp5H+8g9j8TdcvdFk4jZfLwb1HfSd9tA8WUDxQKYFziOQMXOMHBM4pnNsw
MePORTyWShULH0k+rE9VRpeWaneUPu4cBZMtDNKDgkM7wldcXqeIJooohbFIXP2ptGnq9+SS5laK
44uhsC4il1L3IZ8t+pF/nGEoL/j2CQ9yPMhTThVRkQplUqmUjur6rE5Tugg+/rK+rLv1ycKPniBk
fMeJz6xMz2A8bhZbM61aqO24baoLS3AiM6DCQG8RLMFAcOnerjfuqG7XSnd0F91/7PiG+4Yy6T0R
KdLXLwc+sWWttL1X5dyBtJYyORRhzr3xxr2WObItXNi/tvN+EyQ2EyWu9+CLH09gmQW8HFpfof8I
eBlwDXXwYlYJXqoO1lAaKfj9IwW/byTENdb04+umITTW3yaCK2C6G8TjwoCXNQXDJZXc6LgbHXEj
d7aCECp61SeT6GASJbO6hia1KY3WJJ4abdZqoFQVaKGpAeWNYoiAOi9dXRKvtvnuDjoGDcFkXcVo
Uiq76eKAt72MKu12oy+4n3bT7mzRuzWJDiW/lKSTWYlHuMJ/OBpGiyBUBzU2SLymKeHGNKuDHV5r
ttsmKF2thg+x2ayNik3JhgEoCkOn4LNUi5akssPbVp63lfC4/zO5efGFjJvzcnmuMFmdqtarHqHa
QLrzPFDklcCVYDPTzP4pfS3zZ+uG60b6RuaWxUujVs16ou+EdQadoc8w9Uhdq8fridN9Z8oBAQk0
x/j8ngRnvdb7uzSbYKJhKRHtUQtxa843x83rZ9NnM7xUCuStXdZYdaL6VOEp61Twx+lz1ZvMjYS/
wA4kqUt0EqVQBdGogUqL1KVyA2lOqKgk1UvxpJbSkKjp8OTwoHopigd7JSmTDvAuwSSNO4l+S5Ur
xQGKwg9Ve0ZVlQaz3QlHK/jB0q9LCElvGm8Z7xqM0WDCDj8loElhSpgVGKGBRhzV1NRyikWstWCi
SXPKrJuMbvabtPlLpFODSP/Z7u7H8UBr5jaxsKu1e/curhuoNm5XQP0X1xF0gcFbKzAOwoTN7YrY
6mTVmA3egQM3nQnw4UCAfz5YLgVPiM1xhRLfud2qzSCxdbvV7pNuG0Q/L+u+wBBVGif0n8gXUroY
8nhTIYi3ngKbgE84maC8eXcCtan/2WexQ4a9fB963xffD32Yd9XGIfjCpwoX1QW0QC8wC/z3ArOR
WW02PpuY6/1OeqHPDyamhKYp8Dkwja+kK5mvW/OZectdG8fWJpTXVduXV23kcDYNRxyM3iJna9jv
qZxdhksWOXy2X0xKo0Edn0DoF+M2aVQ701i/uSjb6Xbjh+YXsm0pcnstqb2WIMEWEmwh2ZYu4Xve
cwQBpgk2IwZgnwBe4D1HCsA+AZgDhxIiB1X6f3/wbMYJXYXSmI/AgcWisVibt4jWpUNVrH0gfbkM
MWpYL3GaoGeN3JP7tn9aT018+8qlL3/qiBGJBQwj8f0D2/Y8uvaXvr75p0ceqIZEyc+cW3vt7OFd
fR/LF8o7Dv7gxFyS09COb3zzYXvb/tmN9p7p78aEoAIcFl7/O73Z9SoVR6sdDsv2OBJwWI+DCYr3
K1i9/BEZuWXSlYmQyY31fxHBk7HyEUuHn4Uf3yPzrCVEw64Gii9SyANKtrq8VGk1Oxp2HTxZ5b/5
SY2RlBsl58hdfXgfN0k61bodFTpOGPemeMQLcRR5PIx2hhHZzgEowt58HLmJhXOTyOsmKuiGAv9G
lsCVEv2DzgcXieGTexJ3Rd7lJezcV5drtcviktistaNuqQSvNf4yFYAC7vHbE2iCpkd75kJz6iuR
V6IN9abqXehBpzU05h8LTPgnAv9UIC9GFFNhohFF1RiET+H4i4iJ9HeqZfppGnn8w7jo6JuRtyLv
RpjIY+H46xTfQO84lg7iWa70nO+heyiEXC53JvyQjOoyomRRPi9flpflt2WPPJn4yemugVslUVas
3Qbv0AKegHC7uoKlU2zB0AoC+aTgkICbwZIRZzaD02uoGkmDFcMwq+KEkMsNh9LDI6CbG9Cua9eq
eWNLyEzXt5b3Fr+14VhfrOB6de0P21d/Or6lkD9wsDpxkP68EX38vtxjWBlpSKCrzAtUlu7voCpq
Ohg9QGwYLIjX8/infscP6clODlhxZGL/NTJRkxJ4ntSFm9RNDNC5fQFPlDLdgBBUsh5eDyqeHivI
e1n4hi/ggMByVOV6aQneKJiGUbH1ThuHSyXSXL5euttH7fE67CQ7xTIsx+u8EsxkY7Bqe0kesRg+
iMPYQQRUSNdc+JdGLJbG4WuaxLI5nSBP/w/d1R/bxlXH751/3XtO7LvzOb47/zr/uF85x04dO6lL
hF3WNC1r2jJ+LSCrRVtRiwRqIkrbqRFGaEsqQEWowDZAqSaxbprQ+mtJuqhbNg3Uf7L1DzptSFUl
lE1MNKNMZapYk/J957QLgtm59313Pvsu9z6/vn63fdAMuNuPXOyJNB/Sj+jExZ4omsYa9gQ6wsAv
wo47LFAg1gGEbhCDPLhIHbWKzL1gk5pJ/eGM6a0EB9KbtG3pbZpP5SK7aH+Q2ZXSzRxnos2BFLdF
C+pJbg4NNSKE0XWwJPr/hEiQBIMZjTYGIeYMQmF0EE2jt5AXzbGXGrqoqHlR3B35eYRtwXAm4qGg
09ZgB6AzXv/hf+c0sCKAH6CPoXirt4G4TO/8flID6+DjibCQCKsJhhfifDLBOIgfBLdgmqjpAlFy
g3/Ml6vewyHktkA1s4ZO2DOrnkfCma60GVr9sOcHx4ZGxgqJgW1o82jd+e6DtW94Tq5cnR5OCLmx
11tfGP1pCz21uRxH+spvWrv7d7CBnQOsDhgVAKPLgFGNfa2N0RmMGVX0S68AngTYNNhYz1/PMiBh
y8s3btRL4AglWIA1rGyQCY5zGGcz8L2g1EXXV4r4hW43bot+1j0C/NbciUZ/Z9H59E9sd4rXFqFv
pMuKxS+Th+VvKh7QuHfOBatZ6kLfilYlRVJzOEsygibmZU3R1E24RjaJNbmqbFK/yG3HW8iQPKRs
Vw9wv+Wewr9Tn45PZ59nnuN+j59RnlGfi7/CvYRnyIw8q7yszscXslflj8nH8idqzzRG9Crny3sr
bnU2tGvKbtfh4XY1zXbN5dpVENzaaCiJSjh7jBlH4+xB3zHtR77HhRNZvImrkIpci//Jv5B5Rw1M
kePypOIZELfJbESWUhEmrqUYkQgpYMETjQJWFU1WlF5MJIxJXFXzmIMZF/D7vF4OIllEhNjE+FUl
KM8hsKc9BPEkT6bJDPkz8ZEJHKcg5hv+0inuIvcmsHcCK4fUeRRnNAbD/YbFCqb3rSTdeq5cpWW2
o8rgBWiX5tCrM3wWtbLtpwFn0ToTjlQyVFgV3nHGxm81qV6oK/L7CmBevqUu0zouL7dbExfrVF0n
23Fq0leU3YkDuWoZ8QvrR3AUSO1j9xKBC30HjUO+eYloXZ11EK+/zULFecjL0CxASiFQGiRS4zSI
KbChtiPRMDE6GslE20EiEoHUYEKsqGaifuiAUA4ZhmmYAnoxYdrRq2/HuGC2gpyKlEuszturF7us
tFD2nNQNLde76mc7NyZDOBzUda+Q2nrnQ4+vv8RjDtjSeXfJdwHYUvAsrrHFyKSEEFuYo8rLYEPm
vJae9of9FOb1eqkUq/ErV+C1sI4zFxkD3HML1T054bYU7gh9EhCEa4+ygb2M5f740QIqMId0pAcP
WcgKtn+9UOjJZIo9lDqglfRa9Wa9yV9ruhcT3K7Dfarxs2KRgjRRr3aZ0GAKuqkV9xQP4IPFD/QP
rNv6bauDnnAuUnXPuxxPVzLFov1of1JR0vEcX/QSI2kUjJrx1djp2Gn5tMEF9YH8gLmL2YFGAtu5
4fxWc8QasacCLb4l/EyfsqbsVvFp/iQ9WZ/nL+oXrVeLl/XL1rv6u9aVYprxeQP+qDeG9YCJLb9d
jT3APyDs9j0U+Jr8kH08eIKfko8rx3NT+pTRKsYm8ROxScPTiUfRYf6w4AVOwGrqOkEBYAUfE1K8
lsukNMYupJgwCaXCaSWVSgOpznOWCWY60WjIel7jAhwO5G1Lsm0L0KCbvRyWOA5DOlGieaJLhOi5
fL5XViRZVmwjp8gxAvwjsA7z6AaQKIVunE+jsED3eCYE2QRckOfTaU1jWHoQMQU4BUgqz6PvMDrD
oWcbYasBN5vPW0HtTngfgZ7q7IUFZp+dm0NcI9qIl3Yr6JSCLilvKddB9X6RLwG947NaWEc8LDql
YrCjos8jnjGYKDC8o0FKewzUMFoGa0BAuoAnzBL3MtCcgzhFNMZCLeumxVrU++Gr1qkAFYb4bhu1
bMTYvK3ZDfuMvWBfsQP23p77qWn5ltMcU9TllSVoesbWuA2HVDgAH8tLKkQpulGyU6qrNE/VB2nE
Glx7t+fL7T4L2N9WgRCoAHdPDrj1R5z/Jwz/OwZ4bpAbdAVjDDVBKcZpC9F0qFYYvNRRp43JeagR
qhPJWmxdkWi5eS5W02mJuntno23poK+2cvjbwmFSnWjLxj0hWdtHOU9bRzpRC2z4jT9WZLNrEF3Y
lpK4K69JZg1lvm6vvmm/t/ovffUvyY2DoCfeVCJdWPkn+sPkYCzk0XVPjM9J0ZWP0Cf9WiTF6nrn
gTt/Z7evzHrY7X2dNDN2rG713AKFKbPZtcwIHuB0e5gjJjKT4MsyjXsS6M2M4E4FOmXdKUunZXda
nrtn2c6ycwPe9dJiE1ZkvXOnsMMkJYF9rIzKjAiaknuMXiMsSX0MU+m7Ly3Xmm9A+qLKskBTzIbe
M/yDX3n4EhO/e5tR7t5kVHichN8Ir9F44wXMi8F6yPmlzUYqxa5H+3/se9zPYuwTOYVTsSOpBs6L
edVwNqJ+sRofFvfj/eSA8m31kfj+whHuKDmqHFa/Hz9SOE6OK08yT+Jfq79y5pkrlff8OWC+4xS6
uwly/VChJloor5mowWmKqvZ2EwlOKDiOa59ON3ylW8VewhWgKsBnLrdmpCaVuxDcrVnK1ZLhSiym
KpST8RMEXSc3CbuXHCT/IB4yUce78B7swRMQH0ONpPN2WENhbVpjtRN7CqhUqBfYgtJXeT7zLGRB
Zyf44chSc2xp5Rb0H82xlZ1D+7a8z9RHVpacNm/oQrj84NbxAypNQp9Jh08pgMaoVzqfZXiu47mh
sVrp7yvH3Lw4gAwX2h3ohWhPT+b6ohDgsg7q1i0ZK6s/6X/xS5/bMdCbqVkkNZzfvDobzih8rA8g
bCbNodUy+rdtiTjYCZYoZ0L1O997fGpLobuvK/z50Wn2fLqY6+A7/sN++cc2VUVx/Hvfu+061rVd
1/1kW9utLV0G6/oTCgM6GGXgGHOUuQETiQxoEDr3gymajJj4I8EYY5AQEo1BYobgBEVoAwGCQgRJ
5A9RY9Qgv+QPh4RME0JoPa+t/JDEzWgif7zbfO4997x3bl/POfe83kQCc+jfZEwRFmxooWTOwNc4
AMASyBYclohF6LIctQgWROM39jdUCcwSEz5ApfT27njaC5Gsf1KcVayFFkbUMUfAukG/oWDAMeDa
6FXMdbXbF09snxK2r5oUntKX11XT5XzRkbVQVRMVZwfUzuXOiHPAKTr97hlRsTVgMJWbze46k8e6
Bn6d3+Sv8XN/VAwFdLogxOqg1m10O9wz3dydVBYGVZk125w+k698G8zMHGWTAuN51T6tz+hz+Gb6
uO+KuiT4Dt/Lj/HrnPOoWBHINgSb1U+oBfWmWaElyQo6fLtDOmsmuSQVyWESkt1ILW0mOndSfDsc
l5IHgKnMqLdqbIK1zJZvG2dV2oqtOVpDL4yspJcVZJJUlEFSbraul5WK1OVlFfZivII6qWjdqV5S
S54amIvr8wwCryi3CF6P3lJQzoU8g567XRa91yNYCnIrKEHKKTsoY5JnC0oReD1wu/JTOSKO+5iF
jh6OD0Wj8Q8PH2Whj96Nnx7azTyDg8y7eyh++pBhguWt9S2bKsvsB978tM+6eeTz+E1W+F319KYi
tS4/S7H2YHx3LBofOnSItURjbPHB6YPxU7sG42f27KFVdrHJg8fiV/v76v1Vry386tSO3C+YGDvG
tOpiVU4JJUziGjvBcwQN5UJpjE4dEwLjgGIFW83nNpCHLzfpfodjwTDtAbPXzHNu/cAr2Il5VDVr
eZkQUYSp4LUFzBv5SS70oYf18y5Fl/Iz8ST/hv/MMwVRKZyDkiml6BbwLwHOtQITtgyQrihDtcUs
xVHavgtud0iFb/iXjuFkwZPeOLnu3AprRsXN6BFj/NfLZYpw/JNz55BuG0ZHeD+FWE3svQtvIgYB
Be7hEpCxH8h8I0VWWQq1IUX29hSaNYD2pQfRa1LkvpIib8n95D9/lwJav+gaUGIHSusB44wU5h9p
434L2KofxL4lRWVtmiv3M+k8UGMBXC8A3hDg9wDTokCgGZi9CQj6gIZngMYLQNMRYBE9Y+t1oH0Z
sMye4vE24ElKis5uYE0+sJaeLfJeiu6V/yM7/h29Ox9Svn/46GuTkZGRkZGRkZGRkZGRkZGRkRkL
EMAgNQNESWLFhBKjNjHZZyJLDWh1OWSfl49CFKMEZUbpkgU22GmcCDhqnC43vL7Jkr4WMxCgsX5O
cG7DvPmPNC5oWtj8aMsiLG59rK19CZb93bfue1C1efRnHWt77t4Jx1XqPTCRZKDehkpUg34GJsNP
v6IOszEH89CMENqxFB3oQj+exVbswogpN5Ega1PSBxPhTFtNu2PViJa01Qp032uVuDjWD8YnLiRe
Pv92On7/vImj3qHCqvTqIvkAaVnyhyEtK0myS5nDM0ljJ7+kZAEarEzLIum70zIneXtaVpJ8vLF5
VnB+fVUovK6zp6mzvyWybsX6serIi82YhSDmox5VFIcw1qETPWiivp88HKH5CqwnqROr0Yenkt4e
q9V/fR95TGHHDfJRBArykA4OtJLuNOWKSHNyDnudrqg4SdLszxGrBD05/077a5hmUqM9ZcKISlrm
jEoj9qSjJVxZfXZoZ2y5tvY3VZEqefeOi6XHpTG6df/SW723X9VNVWkgbWWWiukfAwDRMApVCmVu
ZHN0cmVhbQ1lbmRvYmoNMjYgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA5
OTgxIC9MZW5ndGgxIDIxOTI4ID4+IA1zdHJlYW0NCkiJfFUNdIxnFn7u+73fTEQSQUgmCf0mQ2ol
oYn6DyKZCVlEJEripzsjE00QmVZYbCsVbHaHLupnu6VKSqmf7hfSUopojx5VfzlU1Wqbo9RP5WyW
tazKfHtnqGXP2b7v+ZL73ve+9z73d0AAQvEqFOSMzOueUhiTPxN4TmNudmGpy7MlcsdSINcN0PDC
WeXa37etPMZ3FwBzv8meF0qDru7tAgRFAepXL0ybMzml79urgB6dgOA3i4tc7i9i2j7F+jz8plcx
M9p82voIG2zic6fi0vLZpa+OPQGERQAR66eVFbrQY3o1MKCOzxtLXbM9IVaq4vcsDm26q7Ro1qEP
RgB5pxhPd0/ZjHLGzStP9997XiryDLa6mRNXC4SXqXsRG/g2I1bGIxYwLv38+UqMS/47/39xnbV1
ePA9XDuxHV9RF9Kwi+4hEnfJQsnIgsQdtvhXNGMVIjAaq6kNOqE9A8wiyTIJWEJrjFnGNQzA66g2
dlOlsZXvl+Iz3GUE30pCb2Sz/HMowjXlMgqMNxGEKrREf+RSe7hwlvdtxrACK3GAXjbustUIVLK+
VAzGYOOQcR9dsUQuU8+1+ADLsY9MRqFRgo6Ig1ckGGeN7xCPAryD7YwpgerkUFgxFYvwBlmUz5ha
hY3wUYiYqGSoB9lSFsZgOn4LL7biKLWhHPWc2mT8zrgCE9qiC2MqwTXqSSPEJhliDDTOYzw+whH2
17/r5Hi5WR3vG2S8ZXyCdthNwfQxHVJT1D81zzc2GO8jhPEkc0Sy2c4kLMAhfI5/4KaoMCowFHls
+TB1II3iOeJnhUXME/OU0+jG3k5ktDPxNnTOyF7sw36Ozd/QgMsUQTH0a5pEy+mmCBFucVJZo9Qq
ZyTJ9zjeNnTmGJVjEz7EMRzHSVJZ/zOUQ1OojP5Mb1GD0MUNcUcGyQXyJ9msxvsafD8Z2cZtRCEa
wzEXFRzbd7ALtTiBL3ETt/AvCqc+VEwbSKcGuiFaiDgxUnjEarFJ7FCyleXKIdlTpsup8rg8r/5e
XWx2mX333/Wt8O3w1Ru7jXqunTDWH49Mjuh8ropNOIjTrP1rfIOL/vph/f1pHD3PVmbQH2gl7aDD
VE/X2UsEdpzoL+xstUy8xHGqFCvESrZ+kvcpcV58I34UtxVViVN6KS8qGxRd2aOcUn6Q4TJedpPJ
cqQcJw3OTIo6RM1Tt6jb1E/UJlOqyW3ymK6aK80Lg441d23+1gdfsU/37eLaDeJKmsuRWIdqrvta
zsFRjugJRtyAf3IWoslKTzPuvpRJw2gEjaUJVESVVEWv0xu0hqrpffaAfRBmxp4gBos84RJFYqGo
Eq+JWt57xefirDgnGhl5pGJTEpRkJUsZp4xXprMP5co8ZSFHdrmyVTmpnFauKFeVRs5apOwoZ8q5
8i9ys6yV9epwtZR3tXpQrVPr1fvqfZMwRZtiTd1NU0xbTBfNJnMvc475j+Yz5ltBHoqlroxcw2NL
WLgHO4qtIkJWUCMzOpBEK/Y8gfOQx11xC4MUH+clzH/P2NoJi2zrf2lKkzx/RDntQ086jAqTUHiq
ygbspAuiQX4qBuBLcpJFblamq0eFFdt4Gi0TH4t9lI5akSrGiLUK6DJtwWWu99lYSVNpBrZRI/Wj
V6g3VeCMaK/k0UKkGtVCUgvKoiYwAsyXbjyPX1zUl6f1Nd86GSpf5vm0B6s5o9vxHb2He6QaN3i6
KTyNXDxllnC9L4J/6k3kPqvgfrTwBJlmOolaMvHE720aKOeiCf/GNXUvV1Q6T9IrvhK5Tn5v9DaS
uMO4y7CF+64YQ7hjLnOV7Oez/zSBOz2YZ0kKd3UOxsGNV3jqLTd0Y62xwJhjlOELfnuPEukereeO
2MMvUnGE91J8TYu5D4f8sp//b/ncqMN1iqLOlML90KjOUpepW9Va9YB63JTM0V6INVzRF7mag9mD
QtTjOu5QEOfGgkQ8y3j7MPZ8TBMFyn5kUDQ83LNdeI6nP/RkBmup5Oit5X7ez73RxHNiAg7gHAmK
ZI8K2X4Q6xnGcf4NS7/LGVxAu5jj5qndFT+y32HUR5SzvTTWtJqnVh1juoAfONpGAFcizwU7jWFd
dzAWbrbQCzlUg0zjQ55U2bArxzjenSgc6RRHG/mdkzs0DB3QV/2eBBJ92UYfUaLs598Yg/nr+dcr
BgPoRUbRiv1oRjsaiZ6+XMZwGkgbPDpt0MABqf379e3Tu+ezPVKSn+neLSkxoeuvujwd37mTLc6q
PdWxQ2xMtCUqsn27iLZtWoe3CgsNaRncIshsUqUiCIkOW6ZT0+Oduoy3DR2a5D/bXMxwPcZw6hqz
Mp+U0TVnQEx7UjKNJSf/j2TaA8m0R5IUrqUiNSlRc9g0/bjdpu2hcaPymX7NbivQ9MYAPSJALwvQ
oUxbrfxAc0QV2zWdnJpDz5xV7HU47ayupmVwhi2jKDgpETXBLZlsyZQeafPUUORAChAi0tGvRiAo
lEHp0Ta7Q7fY7H4EutLZ4XLrOaPyHfYYq7UgKVGnjELbJB22dL1VQkAEGQEzuilDNwfMaCV+b7BY
q0ms8y7ZE45JzoQQt83tmpCvK64Cv43WCWzXrkfOvRT13yMrb5ORX/X4bYzidUSVaP6j11ul6XWj
8h+/tfr/FhSwDn4rOmc6vZlsegkHcViextbEooJ8nRaxSc3vid+rB/4V2Rx+jnOKprewpduKvVOc
nJpor47cOdad0dFpHxkNiHZo3tH5Nqs+KMZW4LLH1kTAmztnlyVNszx5k5RYE976QWBrwlo9JEJC
HyeKHt0FqIC4nxqW+yiy5Edky+KC0LVCjZHk/4f7qg+Oqrri571333tLpLotTQrJCEu3SQMJDSCf
wcpCJhGbGhNIwiYwuoQPBWqhZshIZwgpYyVuSMs3gQRKtYomWDfIH4uh7VI7RbCpzmisQx3HQmmB
QKeOUG0Cef2d+95bNiuUaqf/dCe/nHvPvefec8/93XPv82NN0/jf0mkUXjwN3fCrUmAVWYIdWR4Z
UhAKe/NZz/YRPdPr94WvEBjgv3RxsGaRozEyvVeIi8yTONXQ7pYjOTmRsWOZImYB9hQ+3iPrk8fl
1kXVKf7VXh8EwkeliO2iqvw8hH/0aN7gpmiAalCJNJQF7bqPajIOUSAvpyqihrgl5rakVnBLg9sS
Nw/5weTDxI/61IgnK/53hzdtWOEj+REl7d80L7Xbi+f5i8uqg77CcMiJbXH5oJrdPi3e5pQiwwqC
WobqlNQMTbaClAvjnbkSHBoRmfgzJKmXRDSQUioUX1HEG5pj/69KGT36pjZR05NgFLX+zlZSXDdz
vIzk5wyuzxhUH+Td0LAGf0WWWlxeHQ6nDGorQgIKh4v8vqJwKLwoajXU+H1ef/iIekA9EF5dGHI3
NGq90pQRKdpUhUU8ouSDrCrN7vQrjWWdAaVxXnXwiBdfKo3lwUOqohaEZld1fg1twSN4igSkVo1r
uebjGhUrIPoh1SObMo4EiBpkq5AKWV8cVUjqPK5OocVR1dZ5pQ6/ccR7b94zUEIFXurrGyjzFko2
JPz0bMNRqdMdtFNUe51Wi1r6ElBk3klV+nGqVv5KC9G2EijQ7sQ31kGqQP81qNdCblOnW9fQvxJ4
GrgLuB/IAhYA8x3MA2bB5gTQjjEe4nGkPEMrzG76JuYiYCewCNiuV9IOtO0yplMN6zHXJozhR3k3
9HuNdtqCcgvaq7ivlGxfSd9Cey7K2/RKyzKbyYSOUL4GfRrm38o+Q2Zh/lpRa11CeSzGvg/tGyEr
IMsdf4fL8hm2kWvlNT7FZcSnHvotwFygCViA+LD9eNiNQr0Z5dvg1xDIocDtAh+t6HM33ooRyHGY
v8BZN8l1Yx3xNcF/6dONwTGdlQj4xOs6D3QDbyb4lozmQajFq+IuuX+85i8AM9Rumo24DPC69LPW
xwwP0btYVxeg4z06wUNWO/ycqR+mFtQnAndL1JIi2miVdhl7cJi+b+ykn0JP6gTgH5SpXqR0I5Om
In5BjD8fWIoxX5V8WMI+WBchR4mzlI6xQsAKzH3CjRPHBvU52Ncg+l5FGY9aegJYjhi0AI+xf5g/
j2OOff9YqRx4AX0/wDzFDMw5SgJrt/eV1sD+exhLkfPY+2BLAO0rENOfA78CjrEPLiTPHMix2klT
262PIIcB6UA3sIX5BoSA/dwH86egf4rkKzjD3GR+MDf045Kr89h3ew3yLDQ5Z+ZR2C8ARgDZxkFa
6CAbfTk+NcxZPi/u2Mwt5rUrJadXMu+VC7xO5lSC3K7HqIx9kPOCW67kc4dx17LEdwn7tEfroc3M
WeabKzkuzDU+j3wmHFmasNZc54zkwn6k5Dq46Eo3FnH5Bu3BmJXGFvC0l0rEKSrBS7hEXwu5Fes7
Ah3WI/BFoeXQA54YjcFePgDb3UmyhWH2KCsw149FB2LRQ3tlXHvUr4oeRdc7rPM6KSf0DrVelj8l
k6HE7DaWjMS2z6r/PFDf0TtoGcoX9B7Lwnq28pkwe5XxgM+V0B8CGoCxnhylxbNSiZoV5MUn32Vg
lQhQvh6gqSJGM0UqBRCnTOgrjHtl3t2M8Y8rvdSM/XrSTCW/dh65EXOp7+B+AHh8yPsTeDSIc8lc
cqXL12TJnOG8C6lDjsC5ewXoAk45+BNwGnz8rjy/uBs4P8v7ATkaaLb5al2K8/MEtUH+yOVnEk/H
JvHTTOZlsuS7hfO7vFtwTuFHs7t+zo+c4zhHcp7ju8/tnywT7Hcgd/xB5uFuqnbO9RhgPJCHMY46
eaRLi1qXcUbPGW9ZXeZMq0s7aXUZu63nzJXWa8Zhqw3rHhO/U2N2LuPz5N6lHCe+F917VM+iZU4+
2yP7Yn55j1bKPEDGWpy/FVSDcX/H9yqfQ60N5w7xxHgbxPP0HXGaNsP3O7SXbL2YRyWcE0UdytAj
p3P7bdpm2T5XfER1YgzKz0O20hcNk+qMX7ON1S11Z+w21unVtAu8yxNP0c/0TgryXvE61MnWSd57
nPl0TwPtNQkcPk17RB/WHMMaj0vZKvnEti9bfbw+cwZ9RdewPu4DsI2+l3xOPHbKWMRkjHZIDiMW
PKbxtnxvkP4u+v+E1nlSaI/n68hPVyjdRC6Rc3XSfE9Axl3I+/pDnI9ecKyCGvUvW/+U/D9oWVof
zlAvzhcDTzs9lUbovdSKs9Qo42PLJj4/Wi+lMkewvnL5nugFx5+lx4wO2mTEwLse3AU92LderGUl
TUN5i+iw+tG3EGMQzw19mXyf8D0VsN7k82LGaLgZwPzowz7I9x/m1c7C323UiFwyy9NLzxg+ftco
Crg3EphgQ9bXA/XAJhtS57WlMhpjrJP6pfSa2q6p4De3nxAv4Oy10iztAKWIZXg/XKANah5t1ErA
u0u4MzTYoS5yKVu7RMXaJ/L+2ain0FTZLw33+DkqFVWwj9EScYiWaBbKw4Ed4CPs9ChV64vxznoQ
4zhQp8BmCJUaTSjnWQe5n5zjEyuNIdbSRGmXAOmrC/b56QSfdyC2PwAf2F+UE/1lX+N+Oj7eyD+5
Th4XdrLPH2kWkfUekGnLgTK1mTqA/eopvMNjVK/sxGOljYqUs0CbgxdpjpSdQBkViXqlESgFhKin
fZDjIC8APUAbcBT4m5hMP8TYxyBf5u8ChvpL5C5ItD8L/AJ4321LBM91I30ixF9oUF2fSOsZai7e
hLn06f77aJJ4HHl4POIJaHVUyjBup1Wmh1app6HnnJRU17Npl1hFI2/lz62gvEHjZQxtBBLX6O4H
ZNp/gPcSpI8lztc4vp//Wx8/K7C/64GHZfz30zckh84h/iYNUY7Sg8oH4F8bfZvh1EMynvtw7p19
gr5R6pP2D1yZos2lQLIe5Q0Mt568r7eqY9yXEuHywIU5EW8RQLyP/kByHffBkwyDOZYr6+sYbj0+
781QTpMQpyJIkhxLqhteWsNQV6PeQszzRxnxejneVeU2PxmI7XIGYkgM6B5mIHbEQN8nGAlxDXJc
MSfbkrs/Ls+T94f9Er9Bvz/jzVxO6ckyzm8nXwzifJnN93idc8nZpD7Xz8T1s4GzcrMx/5+As3MS
OA789n89F2cZzhFezhNv4b0RwVv1GXxjvk7NRNcaifqPEV19CHloAuSL0FWgnAX5ITAcuuWQuI36
wbKrYOPA20A3sF9k0OPOu3IE6oW27bXnnPEybXu268Nrp3+Kbd+/EWhF+fcAWNb/KuR2yCvoH4Fd
FWQ9dBsgJ6Fe+i/Wyz+2yeMO4/fD8eukcWxCCC4h3AvGdn7UjXHDDENKXqcJ1epNcSFFziiqC41U
bVKxRAIbtElgikSCSLNNnda1atxJi6qxNm/Og9pLGO5YpapTh7epWjppmv9gf0yjon9Ukya1yp47
m4K6bm21BT333Pu+38/d9707Xt9Be3H9O1z3QAz1L0N/g5Dnh9jGfNgF/kXouNqPfMo59P/r/+H8
8XkdOX4DOqT3nMj3k2eIz+235vMz/JNnjVvz/1l+6yzxb14dB+z53lK64+zzX884txzz+c+qPoBu
OqbXPsKe0tD7aOxl9Z5b7R+rrvfb7+j9JNV7yqpjPFUe9WrvrPav8BfgUzXXkM8x8lXkdUDl9Usy
xH9EPJQSsVbkP8x5m6JWnj+X86yPWnEvfxa/AM8SRmz+NVKEGDnKv0smIIbwhAzviBZUJVfXEPUi
/hwxoUmIkyxKqq8tSMWfy61vVs1/R3rWae6UjHRXKjmvL5qMN/FvEcpH+JPETwQfh2+BH4G3wg/z
x4lb52nlPN7oJPrrRXgv30Da8TiOPWAU3s83kRYdNiYbKv2MybaOaLyO3899OsTD3aQb7uKGjApz
mVvI1OJnc7V3qfzOSu+G6GU+xQ3ShKhJRG0Unsu8jnRB6k2GcrXu6Fy8ng/hNYcwLAI5UjKvS4s/
KdEQ+hvgm0kznn0Tx94N8L18i9wgisvYrauw76lW0F+PdN2nLOduiBbjtbwHT20+ixGf1b3N5YK7
oiQe5G0kAjEM6gRqE6h5+QxqM5imGUzNDKZmBlnM4PtG+DSeTCOmi58kGX6CzEHzqDvQ5AaJESzo
yva2aIHfzX0YCe8yxo7i7qZcbYPKzCcb1+swX66+Idp7mR8jgxBD8qO5jb7o0WXeoV/lnpyvRQEZ
WVuPodtYmQuAzWoOLvPNfIseiVY9AnZc4JriCCsIZW+xkhod9gf2jppfdg3Xyn9T9ber/tuKrxVZ
KYderDz7vfJyfDP7Kxp7lP2ZzKPG2DK7SiIA/sTyKgv2LiuQXvgqrh+HF+D3wX8ht74p8iyfgyH3
56W7Wb0suyo7u6oVEahWNrZUK43N0XiA/Yq9TjajiT/Ct8NfZ0WyDX4F7oMX2Sh5E36R7SR74D+v
+q/ZilrT7DV2ieyC52SDSsGWhrJF6VT2qiSVq2SXWGGvsgtkE0JfkcFNuPtyLrhdeJbRHmU/YaOy
VTTG69hLNEU/QFCWrConjezHMqYamZMrpiiwOTZn+WJWwApbCzwSiIQjC9wMmGEzZi6YcS+bJTUY
PPyHZedQxojJsHogC5pj09IRs+Mf4Z3UezEyiTKra2mUGV0jKL0fP31f13rZFBmEGNoYhyagSeg0
caA8CZ2CnoKe1ndGoTHoBD4fGRAZEBkQGU1kQGRAZEBkNJHRvY9BikiDSINIg0hrIg0iDSINIq0J
lW8aRFoTSRBJEEkQSU0kQSRBJEEkNZEEkQSR1IQFwgJhgbA0YYGwQFggLE1YICwQliYiICIgIiAi
moiAiICIgIhoIgIiAiKiCROECcIEYWrCBGGCMEGYmjBBmCBMTXhBeEF4QXg14QXhBeEF4dWEV8/P
GKSIMogyiDKIsibKIMogyiDKmiiDKIMosxNLvBR/A0gJSAlISSMlICUgJSAljZSAlICUqq8+qgeD
YdmMQxPQJKTYItgi2CLYomaLenmNQYq1QdggbBC2JmwQNggbhK0JG4QNwtZEFkQWRBZEVhNZEFkQ
WRBZTWT1wh2DFPHFF+UXnhp2mqZc+HFlk7Rd+wS5oX2crGp/mixpf4osaD9Fzmg/SWLaT5CgdrSn
fZQIF5Ui5ok34xMwCD0KHYXmoUXoCmTo2jXoL9Aa22ltc3iMQWPeWDSuGDWLRtlgHuegc9656Lzi
rFl0lp3MjLcwt/6O4tNCntHlBMqbEH5EUPbqWi/rRr/d+M7uxL9u1m2te8+82UGvddArHXSxgz7T
QeO17AHq0F86k8QYEqcpqz7YI1ahWDDUgy/T7KUbG4UMfknk6UrF2q1O+A1oCVqAzkAxKAqFoQAk
9L0OxKesbdUmV6AQtBUyVRekuRm7+sZ1LqvA3HQh94ab1Kp+Qm3glmUoAsvL0CDsNRk6LOK19BIJ
qW0QvYiZuwBflOI6Hr9SsZ9JsQx7WYpu2CEZuhd2UIbeFnE3fZgIh0KHqr4f7618nxQHEPaQFO2w
ThkKqugOdBTA03aaItfhgSq1vdKTX4o9sG1S7FbRLhJSE0+dJKzTq4GU8xwSulmgKQe17hLvie+L
G8D/joHF8njXzDtg1wJ5esCqEyvhFxEcFzJep+Lx+7BUdVv5RbEQmBbPoy0auCSeE/eK2XDehdvn
kfe07kKKM2aeXbDWi0kREaPh6+KYeFA8JvaJQwHcl+IRsaLSJMM0xS5cEkk0+BW8RUCKBwJ5neJe
8W1hiZDYba6o8SW7Ku3GwitqBEi00vs9GN+OQF6t8YdjebrO6jDeN+aMg0afscfwG9uMLUar0eRq
dHldDa56V53L5XK6HC7mIq6m/FrZ6iRYtk1OrzKnQ5UOXfcyVaJQxz5GXYw8SOz1PMES+/towi4e
IYnDpv2P/f48rXvo63aNv4/ajQmSGOqzd3Um8sbaPjvWmbCN5MHUEqWzw7hrs7N5SoZSebqmbk21
2I334yGZOt9SIJTePXV+eJj4mo/3+nobe9bt3tv/KUW6Wnbe/vPdWW21f5DYn7J/2jpsR1VlrXU4
YZ/ebz6SKjAPcw/0F1iDsuFUwZFhnoF96r4j0z+MsOs6DKu5AWEkpAxhrj5iqjB8T/pUGOaoEhcE
jrityhBX5yZBHResc+s4B1VxS6vmQP+SaeoYHGNXdcxqgNwRgxUDtn8pGNRRfpOmVBRN+U2dWLtu
SAiEhIUOodjX6YYE1Z3ZXbdDAtWQnR+H7NR9cXo7RlRimtpuxTS1Iabzf/wb6eukuR1j41cHRvwD
af/ACJS2zx1/wmdPHjbNpfEx9cC0eTB9+MgTyh8bscf8I/32uL/fXNpx9V9sV2tsFNcVvnd2dmZn
d2Y9+5592czsw4/x22Mbi012bNZbiDE2L2cXdYvTgsGlAi+2S6pKAbWUdwOlIaaUFreKwH2oMTY0
dpqoqLShVSq1SpsfUapSVVSQqFZAoqao9rrnzuKIqszuzJl7z71z9vvOt+fOfYr7BnE3RFJX0I3O
zZkrN/QdqakGvaEz8kIqO51MZNr/J9axT2NlEk95WII8LENiJduf4m4n7iSJ1U5itZNYST1pxOoc
JLrvzVyxoI7s6s8W7TRls4KG+4NytsMrDj1LBD27SpZeCr5JIzyBbGp2ko90TApwEldNe007ccH/
jLjs0F3y2CW9tEoOvoknHrtE6HZEOtAytYgM6pps3tA1KW/amiFSmdRfeHrOhslhuCXUOZiCL7RH
jBM+T45Ew089Rp52jI6ODpPLqDqMUNdk1aauyZYN8EtYFkL1p7LQV7vcZzIZfVc4rnNm6To4VfgR
eISEI3cqVoFB3Qq7LpYaZ8ZZimwVRqYD4ca9b8MKfgBO2MdR+6fqGoxdxP5pJUb2LyPTdc1FC/tT
YqcCciNEmG6FqcTGilZ31MDN6djpmtOt47HxmvFWBnp/fgk6yy6RpXSq7pIJjajDy0TA7UgWyIaf
ReL9YCoUNgKPkxtVzarD2ODr/8nGy6R/Suzw46cOG48fWU5IsX8YFQcXnero8qTRx1MM56gxxQgI
pRdKsBk+8DbFoo6rFC4w7AyV1F3ITBdMyMrSBYz8FsZcoExv4Tji8CSWkKSK84nFxHrxQaJ7MYGS
cC8uwKWhXnbIjhhcoNCjhRWm6wu6Gf0HraCvQyy0dukuXUs/iyKwvOT1XWzAEjKHvYHngmtCa2Mf
irccXIs/7X8+PuDfGT8cP+P/duBSYDZ4M/DbIM8wgsfL+L3lTKUn699PHaYuMdeYdxj+l9oHIhWO
NjY4qoWortZqUV2pgIs/rO2NLkSpaDpMUlZvL9GeCWMUFsOT4UdhOhyuxk1Ih94SWO0otEXWQ46k
rAdFuEgBTYb0X6NZXrBWk8yDz7DgNiyMqIYRuu62lTbELZVchZAt4y/yVBmPl3jM63avxgd6NKz1
wwr3cj3GuKlS3ubDt3y4x7fNt9dn8vmbBtslFTjM5fd1zz3Iz+XWi7l5tdi6TWidgxwlE8lFMA9y
6m1nW10ur15hqNWbM1N1YZzPzhUbsyi6dP2NYFjbHN0epXJqNgczHM42k11MJCApOJ9DuTwub2lp
avR6PSa31yfHy+PlDBNR4s1aS0trS2uzFo8oDGYYlvG4vU2N0NXSjHcsqe/94a2ZLlMwVvjYJrKm
Na/lXnu777tnfrOud2/XZvy5lo+jrZnUus4m0Ub9vfb8K9ljbxRmTn5jXajVb0mnp45u/WZXKLYi
tKFzVeE9Z6NUnljV1xhvje4AVr6FEJ0FNXjRRV1iXT7XVssuCw2LlmbRxJQlVfKRaGYIyWEHaxcY
3mbDyErhuBfpK6La6wgvwUMCEsmuV4lqp6VxiRqS7knUJxKWrLY4b4d32ClB4MmIEpgyzuN7kBu/
L5kweM/vUxPd4pxIhAysq/NGh6HnhJgA4uca6lEOyJNlhxYn9DAekLfsARpLKQ+dLdyJbmhbO6IW
7mDziT/lzveUUaU/3bGy99BUoYyOX7i6etehrxLdbwTdnwekAvKjMX3NXXzH8tD10EPfpO6aKaff
7OeorNjn6vNmpTHqHHPOMsbPcO9TH5r/wr3P3zHfYe4K4mXLu9TvmRuWd3jzqOUYc8hicpAKZbX5
CEVumnW3sYH+4FCQCtpl5A9kitrqnlsv5ue750BMBpx8DufyqzM6NygOOAe8gxKNc1kAmXNpToCF
PG4UUaLxGJFAS1ETG48vXriPtcLv/nmm8PA4XvHqnj1nz+7Z8yqlnMTM8cLNT+4Xbhxamvj+xMT4
hYkJgvdE4Uv0GOAVUQid12tXuta4KKdmahPaXFowZVorrHWlgo+CXB/TZ806+7x9UjY0zz4Kwisr
EyCozKyboPLabGKJ3SdbAkOluNRRabeXxEURk62JbQgdhEj+cLKIM989l4BEireX4SYI4CQRP2gf
A2JhgBmwDgLmAWkwxBDQLsgkwewQAXO8HIrWE6hPYKbpZ1+cxVRhYTZzqgdS7H154PNfO/yFnUch
tb3bC38tLBbmCx+ktyx+ZJqd/sn3pi//8CII8giU0lYD+4ReMWbGnB1vMg+YR82mOmfGvss+5KSt
XAlfxlOn+CWeSvI9PMXPUPv1SpYFfZsoxlqBOJGr54Y4mgsccF50UtucB5yvO//opJ0iimOTgZ+C
Pew4prDfkZzFIVQk4Qk5z+f83beRlDR0DOpuayxSkYeV1LeJrPWwklobVwIPsqFpYMLHGiJ34HGi
6NW7U/3Z5z/zzKqNdXR8bHeq+V+17T8u3AeM9aBnETBWUb/SrzMOJmIp9zl8kXPOc+6x8rNVHOtO
uynnL4RZ+035H5F/C/MKUylsEXYIZ21jzsvKLM+2R/RoKr5T2R4/4jziPqx8Pcq1xjuZtO05oack
LXcorBItj7fyzXKz0hxpjrKM1ezgZEko5xVFibBRRa8e5l90f8Xz5crRqqOeQ1XnPWerripXI8JB
fMp3UvpO1Y+qJqsZn+zV5Yjm1UOwkfHiW17sbbLIvbFTMSqmS2EtFiDlXPc5rMnealxfjeuqcXWp
XC9isQnLiJT6Ei5pWBhCrM5xgob86oszhPIFKLRG7X5cQdQ8ae1T1TlULM16M4Mxg704rrTIaXkz
zvq240HfPLZiH0UHZIWqcAk8VRHYRmM6XWHrDeBA2sUmF3PwdTh9bctnLg/bGGXpXXg3gcWpaBXY
Yk2XRkn7b9Nl0WLbHzDaehBudgu4RUkr54RXlF8rf1YYWeEFmg4QHNf8QQ01YYLMV5MEOznNWZ81
2kpMI1YPB0IawvVYx72Y7scH8T38X3arN6SpKIqf+97b3Nxyf7xvd66VI1FnC2bMoauRT6kwdaHW
zBGipimCZYpBSEQFBRWEBX0oiCSivgRZUVT0wT4KRVF9yU9BFhVFEkYg5Tr37RnRhyyoPt1z+d17
7r3n3cs9Zzu/IwNx4qydKLplrgctCdESoJA2ZVqR+BM8Gh7tiTANz2UaHsq0aHkZ49zMtMIS7PBc
B8vXaVBhSZ+G2dvhIw2+tE8yHj/ACU+XqRCfznBazEwzzshspjLcNoDS2sqrKyTCCc1qc1c6gtih
H97dXBSzU3uMq9fsMfTQ26u2GBi1VQrzYW6hR6e7aBkyIv7okA+RJZmJJ3zOhcyjMI9KOVWWEp97
Z+eO8kKqbpi7vHXf5MvJp8G5z662lv7SgL+I3Eu1zHx49pWEQ03JoD8cUKmrbk3z6aN3jx9buaY6
31OwVPV319YdPvl4DP9F+enX0gnTWeSEB1pJAAKkILvEsSqnNiflyMpTwSt7VGDuXEqYW6LEK1uz
srPsXu5uB7BRNsbkdhzGsZK4RZRrKuEp8zqovH4b0nLsNms4OwwQJm2YJdBCC3rlIuZOqpX0HL1C
5Xa6n47QR3SamoA6aYCWUoXm+faMztckdWPlmCdWY564DTQ9XpGKJ3iNN9Mad87k8dTyXq/70HQK
aw1XxIHCcwxRC1xU9ynjTsNCI+oqiEaihS5peNxW7C+u9W7bWz8cs1kPHCA+pej53OaDIf/iyeWR
xnUrT5GHz59cmDsC89In8COk4T+H3IWV1mas8xsyMJcBWHE9+4yAgICAgICAgICAgICAgICAgIDA
rwASEOBCQeYa8SHM8O9l7Y+TxqZNkGze8h+u/W1RoAJ7CzYJxw7YBUPptK7thMF0Ov2CN8N3GZEX
PNMC3cYXMriwJ8ZNLmwZ3YzaMh4JxYoryyBi6BLkQNLQZVzvNHQF9UOGbkb9Un1D9fpETahqsLej
b0V1f1/XwgtQDw1QDeshATUQgioYhF58Zh+swNV+HLugCbZDD+xGvQN3F7b/GxbcI6YgfIQ4vtaE
HnBCGH0A5o0YB5lHRQEygjsWBTU+mx+hW3Lj59/l5zBUooCG1w3pwb1vURXJiIb0queNsutOmyP+
yZJn0a3Pv4gv4eONiYtHZ2e/fHWus6g45fHRT/4mwACqtApTCmVuZHN0cmVhbQ1lbmRvYmoNMjcg
MCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAxNjEzNSAvTGVuZ3RoMSAyOTkx
MiA+PiANc3RyZWFtDQpIiVxVC3SNVxb+9jn/uTcSiWhE4n3j5oVoiIR4NTdyb0QQ0dGKiCWRhASJ
lCzv8Qhagmk6NI3SDhVq6JpcRbyKFFOdCvEYxsIiCBMlZc2qdkblntm5ZvUx/17/Wvs//z777Me3
vwMC4I1lkEgd87vIqCkj06qB4lReTckuyCrKn1VhAYoaAKrMnltsyfJpZB03AQ+PqUXTCj5PKohi
ndfUtWkzF0z9+OF9KxDTBwjzycvNyjm723cd+9vKe/rn8YLfiLY1gM8X/B2cV1A8P/xSZAV/1wPt
ts6clZ2FGrsNyOC3XWVB1vwi73Raz/vZHyyFWQW55ZmFXsDsXRzPO0Wz5hRz3PzMXt3yv2h2btGM
srF1gHUZ0Nap/oBuapT77Sw3ohOg7/DLsepGV7J+oWbA6pqu66Ufewt++f7vCcFKBKMR5TiBSTgr
JBz0KtJgUCA6QNBAjCRfBECRJ8JhxUikwh/JuE/eqEJffEuJWE4hGIMt6I4UtEc83sNWGq4fYjku
Uz728O5dZEMYRlGSvo2xSNUH+QxgMD7Ah+SDbvzHk6z6FnuYg3dwBFehkY4KtZW9pOJ1FOqDyMBF
SqeJujNGoBBLUIFtOIYGWk01htKZiMEUzCYz+VG4LNG7EKuutTqgT+sL8GX7bez1sehlJOrvYEOj
QTqPK+qHfiyF+ATVuEmBFCMT4INoPmsSFqNKhnOMSVjDuR2hRVQlfXQlZzMA2ViKeppPNSJIXVNP
9UK8wvlFc6SlqMSXOIVH7C2RxskCV5xOAcEDveDgk1bibfyFK3eS5TS1oSAawZ6/pFt0RxbKB+z5
UzThB/ybwimflog4UaKimpfrAwjlDG3sYwTGYyY+o1Cy0UTeu0XME0vEUlktbxrhxhMdq0/BhEi2
LcFuzus8LuMf3K9EGk1XxRK5T72tF3G8kcjjLFZiBw7jGSlqRa2pHVmoHw3gzBZRDd0RXYRVpMkp
skqt0wv0egQxViYhl3dOxwqswkHU4S4eoYk68s5I3hlHqbSe3qXTok6Olxmy3LAZ5cYe46TxQrVV
J10XXfVc9RY/fTCaZRKmYiHX+hDLKVwnSZ2oK3saSsnsaTJNpcVURu/TdtpJ1XSGLtBDekL/EYFi
ndgojoq/ijpxQXaRPaVd/knWGkHGdeMnc1ZzF9cJ1xPtpXvpfrpMb9E3dJO7C50Z8XFIYHTNYC5Y
iTK8j4+45vtxDlcYd7fd0oCn3IOfyMRo6sARdScrhVEEZzee0mgeldIGqqSv6A410AsB0Vp0Z+kp
+otkkSFKxGPxQnpKq4yX8+UH8pJ8bixQUSx71AH11NRgDvGofbG5+ZYLrnxXuWuzjmEsmhh5fjxz
0RjGmEvmLufgLZbZmIt5XKOFXPEtjJwqfI6j+Bq1XPs63GCGaom3RR5yJ75HM1wkuJ+KPFhext6H
O5PAaMmkXO7tS1lEJbSGKlg208e0jet7kS7RZbpN9+gZ5wTRW8SL4ZxRqpgoJrFMFtliuVgr9rOc
F1fFDXFXPJe+sq3sJsOkQ06Tq2WpdMr98u/yihFqxBtJxgzjjHGRM09SI9Rkla3Wqm1quzqpvlEN
Sps2mD4xHTI1mj3N/c2p5nHmNeY/m4+ab5q1RxjjaTRH3wO/PBtoohEpykiLQ5z3cVEsz4qNtOdX
FlClHEEOJotD8pj4aHGZvCs/EyWAYXf/HsosVosvUKsuG/6qEWdER3zHfLhRZonjYpMIpP5ysLHK
qGXWWcBxbhe3hVlUscUj7sZkvEEd8C/jTTzh+tepUq5porhFe8RXIpmRfA2V4ig2YStyaQBHl4MD
eI736LC0UDXjbiku4DHqf4nWiGweJuJMgWKuaRB36DCN1WdED/2Ip/4OrcIN+Zyx/yalUCR24h53
/QpFUzfDZXTCRWa+rtjMqP0n9vEMfmME8wQ9w2EZjXSjnnse2fw3l10VyxX0g4jndga4mXtMCxsz
B1cwV7XwqA+qGAnMIu6JfoRz1J2reNl0HR/iXRyR/giRO8QyoeXXhgV/RL0cxaf+nvmpM0WzpwLk
cx4W/cBVyR6mIxaxNIXSYec/SeiqCzjyncxFNp2hN6kJqhfO0yjyxwlmr0CuYrlq5Wpiy/08hzeQ
RGuxz5WDGr5XAimEohhNTWquKlO71X51XJ0z9cV8ntrN3MW7+J5vDQtlcy2+xY+M9WE8PRE8P/Ec
RRLfYTPFBHkMCdQRRcyB4czbw7gG6dzJOeylBOt4nnbwHXIeT8mXMnAc13hyAnjOs/l8D/YzEm9w
1+dgJ7PjCtrHKznoip5cp+fkQ7GimM9r4dly5tkajukmHjBzaHdcETSY7Ny9bPzYMst8Qn+k0l4k
6mpGQgrsshb3Ecy36zCe0Urel8nY8EEXDFT3SCDClaJjRb48Ru35NvRhVI3jm30ovcVRtOE8muFP
YxDjGo6BfMcuQ6raYYsfZ4t7beiQwYMGxg6Iie4X1bdP5Ku9I3r17BEeFhoSbO0eZOnWtUvnTh07
BAa092/n90pb3zY+3q29PFt5mE3KkIIQ4bAmZlqcoZlOI9SalNS75duaxQtZv1rIdFp4KfG3Nk5L
ptvM8ltLG1tO/T9L20tL28+W5GsZgiG9IywOq8V5zm61HKL0sWmsr7dbJ1icTW59tFsvc+verAcF
8QaLIzDPbnFSpsXhTJybV+rItLO7vV6eCdaEXM/eEdjr6cWqF2vOAGvRXgp4jdyKCHAM2ivg4c1B
OTta7Q5nB6u9JQKnDHFk5ThTx6Y57P9lvUpjo7qu8HnLvBnTAY9NzDZOmOHhdcZAWOKtlMFjG2yz
eYHMuLQdL1DAokAtaCkNcVIo5mGahqgJaRFBUdPFtOHZiRJTUeQoUtL+QP1RGaVJg6MmqSABklRJ
VbWKX79z571hbKxCq1r+5tx7zl3OPfe7597nDwbjJWFTinbo7SbpVWZmSDShqJjG1KKmW0wT2M6r
oWOBgfCw0Tfko/ZEyNupd7ZtjplKW5znyAph3mpz5nfem3WrisGzo7Ej6Va/YtTM2h7gqmEcCZhn
GmPp1iD/xuMYA33lvNqEUYup+xDEhuYAZpMPx2OmdBhTBnglvKrk+rboNaxJ7AiYGXqVvs3YkcDW
zDFMatofHJwzJ3Leeofm1ASMlpgeNFf49Xhbde7APWQ07X9hdiQwe7ylJDzgy0oGdmBapl3wTk0v
bEnZREk051JDUyqyEnuk14EQZqAjAE9iOtZUxj9bysjoKEMz/MUl9DI7sSPbzYxowvBVsJ77m648
nx4wPiMwQL9xfbymzdZoeb7PiIvMkxTVYHfKZihkFhczRdxR7Cl8/JKoLysJ7xuSn9F3+wIQCB9t
QGzb4hULEf5gkDf42FCE2lExexpjyXqA2v2DFFkYiptygi3DjiVnI1t6HEuqe0IHk18k/kDJMT35
qf9M34zpNdsqTGnGfzBvSdobmvWGxtZYoMZI2LFtaBlXS9rLUja7ZE6PxhS/bJdkvyKsIOXmVGOu
xLymmod/TZC6c8jtASuFRgrUmr7E6uRvfEoweJedhqyPuZcQt7rZbpoVofH1ynH1ce55DQUOq/ly
Q0urYUwZZ6tFBjKMWj1QaySMtiGrp10P+HTjPJ4rBcbumoSzo0PWb475zdq+OBaxTaoAW2WqGtCl
3saBiNTb3Bo778NnV29LbFCW5GiiKj4wH7bYeXwxRoRWTmm5FuAaPpzA9EHZI0z+8/jS6xFWVShE
vWNIIqHzODqJOobkpM4ndPgr4b13B8dq6EEf/evoWJOvRrAh/d1TqJVLuVySHfTTOXUPmSpRIbDe
Q/QDrZ+a5HLqk1n202zov6k+RoVoX4X6YshW2GXo64EjwGIgCCwBaoA1tlwNrOA5gJMYo4jHEZLo
Ifce2ux6nXyuTRSCbAT8KBep79ICrZyagZByr2g7A+UFsOW7j1MR2t2L+ga0W8oS9Xy1m3bAXo/y
Ih4T68iGnAZkQx/E/JfZZ8io+jN6QiXrBsr5GHsz+oaU47QOcj3keuiroF+Lei36FMv91usoV6Mc
QmzWsF6svZsKgHXo0wA/G8V43bQCtumYNwtyIZAFe45SQM9Jr9IzkF9Wi8gr1o02Yt2bbq0JcpXw
aRKwj+xfOtgnudz6BHgbeNf2re42sF/pIOpQllAlZA+g8/jyJay5iSTYK1z/pEqGh6zPsa73gBlq
J2Wifg1+NrpepGVcB6YJ8Dv1FHz6lNbBFtKepAXQL5XvB8e20gL5p1Sm5VEG1teKttVAt+Aec6GT
WrAfFuRU9X2aA9t8IB97eM6Ok49jgzrvL9ZnfQQ/rqNNI9DM3BL86iQf5ueY895nSZvGwE3rGmxf
Ab6GdVUCD8D+DXA4LvqgP8attHlYlJIAcy8NheyDA94nB0mOUA5wj40C4FXgEPA4sBvYym0wbjHa
M0+6MGYN6vOYH8wNjMX7UG9zJwv8LhIcS56ZHyOO9cAsIFPD2bIxFW1z+LwwZ8V5wVlgPjK3mDOO
ZH4L3p+VXuZ18p6nSb/rCjWzD2Lt4FaazGeesVSGqVjIYipkzjLfHCnOZNL/fD4Tjkz5g/PJZ4Sl
GqI8PqvMxZTEOeVYpORMKsKYa7Vn4fu36EG1gOqVLlqptlKdYiL/jPF81g11hJ6Xf0ch97DgDNZI
T0+QvM8n3SPSDtcwvYRY5qmX6GlIXR2R56kjkst11rrmOisfTMIpp8uJkIaTNpaMdNt/q/9fIF92
naWtKH/gGsHZGaETWCu5P5QWAQFHQj8I9ADFnpB00tMlDbk34jwRfQrsUiM46xEqVYeRE3Iogjjl
Qb9R+xE410UFGPtzOUKvofwGcl+pQjifmEu+jHwB8PiQa9N4NI5zk3BJSIevk8iQzSUhmc/Ia2/a
8i1b3oQMg5MFfDdwfub7gXM0sDrFV4eXBRSGbHD4OZGnNj/X2fy8nZe35BLIqH23cO7O5nOKudz2
md3M+ZFzHOdIznOc45z2E2Wqfz89hTW8IfLwJfRNnuu5QAgIw77fziPIw9YhkQ87rb3uWmuvWmLt
1cqtXu1DyG3WPvmAtTN1p6p0v53Lgs5dKu7RC5Th3KOuLuq2cxrfu0tdlbibkveouD+15fBjm7jf
wqjP4HMozuAxypYPIK4FNEUtpa3KRVKUdbg3oVdLkJPZtofmKzcpVz2KXPeEdV15nJaLe3M1bVES
VM59lUHKdD1CQdefcJcdsD4W4/F9Bck69l/bSis5F7h2irt3h52Pw7z3Ho28HpUKRJtLyE2jlM1r
ETGop3kiDtz3Ebx+MJb7Gs1Vy0UcAgzR5+/k5XhwjMbFInk314sxR0U+mybGHsWcv6dNDG0u1bvf
Qs7kuXZSIkPmvGhdte/sOtyndcqzeAd5iQT/L5FXKSU/7spaG6vUhxDzbrQ9Zb8rWCLvi/v+JnIV
OOI6Sk3iPcG27+Hd8wqtYqj9NF9bgfxYidy/l3K1exGjFtIFr9ck54a+TrxP+J7idwKfl+Xk1RLo
j3MhfOD7hscuErGtA0dXeqbgbmmnTLlfksC9XPH268e+90v8jnosDT+0dblJKQXlq+J+ZdtN+aJ8
Tr5odYn7vpTCyq9wP36EHP8y+DCblssdVCYbVKZm4G32RZS/S2XKL4ETiMEBa1SdiRxeDf1PgCPo
90fEMxO2T9DmF+DBIfS9D+W3Kaq8RGWuR1HPA1dfgxwF/oF+X6A+5Xnq03x0WO6wTojxGQfG/sbg
8bgfsNCR7KuDSX3+OXkn9bf6lp8pHyfxj8fgcUU/blNqjRJZfwbyknKsUT5OZ4Ez8pvoO0wHpSeJ
JOyT9D5wysavabWQA0Aj9vCg1AtsAFT1IJ2GLIH8ABgBTgEXgJvqMsTiOL0C+YKGTwWGfJFiLGF/
DvgtcMWxpYPnmkyfDvWvNK7uWkwPM+Qw3oRhur39aVqqfhu5dhHekoCyjzYwtGm0y+2hXfJfoN+E
fhPqrkJ6St1F993JnztB+gMtEjFMInI3a7xb8BuN7+f/13h3C+zvw8DXRfzP0ALBoauIv5sypAv0
VekdWqmcojUMu54Q8TxNi5x9gr5X6CfsH7jygNJEkYl6lB9lOPWJ+3qnOsY9lw6HBw7ci+n7DPUK
2gP/5r7qY9uqrvj9cJw4zrOdpG1K0vYZ2w2u09TmJW26aCTP/aJjc5tO0b7omkxCRgXWGNA20bXY
ZdM+pI1a6iRI0JpAgTJAa3ofW92GUP+xFTaEkqFJSQtrurUVlAHJugHrR9L97n1OKFErNmn7Z7J+
53fOveeee9551/fdO9suyZAfSDjlGluq7J0S0/bMvNdDO2lEndaBiVpjs2zsId+SYCnYjxK5zr8p
MWO341zVbq9PCdR2qwRqSCTQdqcEakck4Pt9iavq+hVZV8wpx5Lp9zO9zme/H5mX4zfwO0MC0Ktn
88z6LuwXn1jzm+z1PmPLveTsLJ+P/xMf/zfwX7lezP8n4L/ze+Bl4Nj/ei6K/UHuET65T8gz6jac
Vbfgf/EaaSVkMk3IpaOEXMaqmLwMHgb34RtRDf4VEEUbvg6Tq8HzgT+g7yN8R3Bkn0o6qskjhXMl
+qY2wu9hIGfHmZoHvR7x/wrsA36M9rNAEvAD0u+2Au5D/5v22KnvgH8E+yL428CraMOKvrwT+vPA
ZujvA/8E9gJRO94l+F06JM8j17iH/nf5OvePf5ft+waJTPPsO8R/xNs+nWffOabf/6fx9F3iGqzq
ULg3vX3V3ed6d5xPMNaP62rgLB3EmTIgz9HyLCvPz/L8OM3q3ob9oDB/5VXskedXeXaW51dwHXhd
0Tns6T8lK6fzOkLar+Qd3Fq71jBz4LplikV4iXFYdojqBcagg7NuchPR0UDFvBrVQ8SqVQVlxUpb
sSL1xlhcXifGAeYgDkrC9igrvMyYOAqb8inipVS28suWbw5m45OWt9Iw4z5+AbldIIz084MkDzDS
xT8gaYDB/YCov1lOxA9YpR7DB/9x4gcyACd9kFTZJiD9x63KeTL8W8JbrsaNiVijrVi++UZbfA5/
E/n8jr9OgkTnfwEvAr8MXgg+xl8hmsrzScvrMzKYbx/c9/EHyBJ0P8W3EwP8DH+Q1Ci348Jjz3Nc
hCNGvJTv5zuUy/38XtIIvoffLQzdP8CfRKYmf9dyuWV+7wrfXGOQn8M1bw68zsCrSvcO8m0kCsgn
yVkuzcjGy3gOj5lDWXTkSEmvkiZ/XSAQ5vsFz5B56Bviu8hc8LP8ITFXzw/wj5TbhzIK5ntClDRI
sjSPkY+7sLooKn4eFT+vZvuHVbvSIPFa/hMSAxiKehraaWg+XI9iQBvQBaSBXgC7HH8PPe/BJ8pP
khR/g2SBXugOhHxAoIKHlRIKG4f5Tr4DlfANoHYUrQ9aLo/MbIeoqFRuO6wyj9E6yEewIYwgpslH
rar5RtcAf1g9StaaXyMH/FG4ylC679rvAgO3y3cwyDP8IVWJXaoC/S/BpMTLv6cGX7HKyo003n47
zC7I3cAwMA444NaOZ2gnHQCHe5vl8RreAf41NfhzwtOgD/L1ePT1qlrrxdyAyvlWC8qmAf55LJKN
fIO4Q0eCmwQGy94N1spmIzbAN6gH3iD0oN0sKm9QyjrhshfPaqu0XE63RjnWiRKPaq4r/O94xJpT
ZehYjM3qkRrkVwwXXD8QAzJokRU3LF8Flvgd3FBpG6QT6AP6AQdepAF3Ay/SIKdUi5evwDOtwOdr
BR47BTkBMLTfTFqB3cBR4BRQpFo7AYb2GGbohMwCDBGjsH2QJtAJZIA+IA9MAMVkiNdjnnp4xyAz
QD8wBjjwQpYij6Xoq+B+Monvs46TbrfZTNMkTdMszdOOdFHaly4vMZcvXmqYd0mxTIowRFOnK+XK
uHjMZbraXNzn8rtY7kpeFDc3gMwKZ3PDicQ7iYsJXtGUdWaL2VC8jJaTMWAc4GSI+mD5YPnMH/Kh
lrGW8RY+lBhLjCf40Mmxk+Mn+VD9WP14PTcTNc1GUwftomm6mzp0GqWtdCN1dPAunua7uUPnUd6K
teDodKfcGTePuU13m5v73H43y7r73P3uvHvYXdTvzDuHnaecE86iNmenM+XMOLPOPqdTL44Wtxab
TsdEfDV7A0Xtg+wHGMlAZpXmUz15yGFlZ5XdCZlStgnZprQgZExqQFBdcCninMCIE8pP2kHImLSB
ILbw42hLQWYBxo6bCwKxkBlivpA/xEiIToTocOhUiPWH8iGWjzezUZXlKLIcVVmOYuSomnsUcaEB
QWQ7ovxG4Dei/EbgJ7VrtXVCppRmQrYpLQgZkxobEcEmb7yKPYaIHZC9wBjASRSyFehSli492GOQ
JuuxblpqZHKsR9RiIwQFbFpk0wJF1g3VRkfcy3oQsgchexBEWjrQKq0redYt1kjfbnGLTc0NY/Em
fCplKt24S3Uj1Y2QvUqLQrYq7YDy8c7Y/ZCnlJaC7JsZ16E0HXJ6LGc9+HVD87LtaN1uuhmZh9Mk
qSgvqcixI2JrhZ5jL4iwD2TZJCTFKxlH7TX6vpK/VLJXyZ8p+WUlvaY7qF0Iar8NavuDWryU3UZC
aJ5Q8pySd5mekPZ2SDsW0vaFtCdC2gA9TQLouNGsDmhnA9qfAtqhgPZsQNsT0DYHtE0B7QsBGSpM
/ERjC6WkW5RcYFb5tct+7c9+7VW/9opfe9yvfdWvNfvhTs/jo6nhriPlI0ouP9So6Y3awkbtCMPO
RG8XXuIaYIzeTjReKiIteo67FLEbRWIxaIFIxEE1IvFFULVI3AeqFIk9etzFvPQgTiQ689CDJZLL
RGQXut02lYjIFlCRiHxGz9EpEQmCLonkQtBFkVwE+lAkG0EfSHqR/p0kGcLQv4nkXoSn75CwDEvf
IrXsOXBOJFrhfcienb5AWuhiNAtiyizo8yKC5OgzIhIG7ReREOhpm/aJiA56XCSXgfaK5B7Qz0Xy
DKhHhO+R8bpJWMV5lNQqvl8katB9r0jICCmRiIK6RGI56G7R8hpoq2g5I4feSQ9SrGyaJBGV6TdE
MoLujsKDfJ2EVfdmslxFvlUkZEnWySBxja4tPMgauloe7OgqelBFMUUkBrcWEakF3WJX7rMiWQda
KcKoMW0S4b2o3IrCBEvk+3mRhpCGDBQUkefgpIvkEtAikVwLqpEjkVRlYdYK0qKSKhcR6eUTEb/+
EnWTpIpYSmppz6/1ScS91JKjXxL6RTNXQoX+L+KrPrap64rf85793ovt+CuJ7cQJzx+xE/xIComd
D4U4D8dOB55TIJTaLGaJISG0ETSNk4lJQ9ApKhTRok5so906pqota0v7TCBygI5oSJO6QRdp2l9j
NNoybdoWTdMCVdV87NznrGkl/to/u/Y7575zfveee847977zPq1FNiX+I5ER/57IY1kr/g238LtT
4icIvR/GrqwX7wXmxd8PesRfBRAhO8WPAvXibf8xMV97Q5xMbBBzuDBlMCN+MKjO8L4fh10RL9Xm
GcDRFwe/Lv4wIIk/8OfpGl5B8AvUBk40ETgmPu8/KY5hKmQTp8XRQJX4bO1+8elaasguHg7sFofQ
kUM4ZmDwkNgf+J7YF1JXvD9wV+wJqT7EB1WPtodVxdcGd4tduAJUdFAFrqAN87IBh9aHbtAYkTro
nLwrPtl8k8G3MJzA6zm5nv+QP85n+D18BN83NbyPd/Mb+FLBKpgFo2AQdIIgcIJGYAQiEKY0vzon
SwRPr1LOTBmnoVSj9s0MpUhoTcKAwJAdRClh40y8J6I0S/E8v7pbaZHiCr/zG8kcwEspiCszB0g8
41Ie9njzoNu1T9F6I6BY4yS+J+JAsMKcygPZk8zDKh0x4VSsnclpArBp4qyT8q6Js6kUsY13ODqs
YUtrV/QRpG+NxqLSenNI0lfuqpTvx3uSyjtVKaWBdlarUnFlY4+rNznNDDNPx6LTzDOUpZLTMMQM
x3ZTOQxFUwhrU2EkzDyDMJKgDGFMLwlTGMp7vwSDHIqjuXC4AHoCchSEm+YJFbSvAOr8Mog9A50q
qJM9o4JeLxgM4DrQoEwZwrTDJKAaDGiHVZiDwnJ+P8406KeQXIMfATl/g6reta6uLagvF9SXqToP
sK4P+QurrSV+1YKfqUWM9H9sA5H/YRBMto8fScYGvLE+b2wArz7lzPiQQzmRcblyR8apwqWw/r7M
gSHK+weUce9AVDnijbpy7clHqJNU3e6N5kgytieZS8oD0SvtcnvM2x9NTXafbBn5iq3TX9hqOfmI
yU7SyVqore6RR6hHqLqb2hqhtkaorW65W7UV3x2B+M5kTiCRVGdvgU8yeh3ulj6nOxWxmZ8Nq1un
ze047ryuIXCJ6KWUYvBGlGK8qKpuW902qsItTVVGFJvWVI7jbW7ndbi0pjKj2OKNkKwjdjiK/1Fs
2ewYNozx6Ggh1o6CIivFVD0CstjLqg2R2KfXqCpd02fJ2HqTpAKWjEqdyVwiEXMcjjqxiJ+kdbeU
GiWSVDAoSQRtotdqoW9TC309Z2v8XeLPiQcJdkat8GfxmlMr/Bms7mfxmsMKfwM7E54Nz4XZmcRs
Yg6x92fvz91nZ+pm6+bq2Oa1FVBTKcAVrv/GpNExKpZA9Vb1G2+z0qhEXf5vDPBOolIaFWwFuTpO
wlmkL8ZK653RgnJMHVKQjq4nMJ6reL5q8Yee8CRylYHbHJ9nBbmEaDW3WaLjNbeBlAuc9jbD3oRt
pAh8sJc4JPPDrctbu82LWxPLW0kH9s1LSLZsdlvcFh8SPMXJkoudWZK15HPi0szQYzyycgE+hEZi
J82y5TMG+CIN/ILcsW436DTxMqwBZD00iiYwbXNcPos2FtOLywukY2FxASytrVs2Q7ok1NQUCtb4
vR6e83r8oWBTY4OtrJQbzB7meZ4zVEltTx18fO+3L69c2NTwkx5LkcBbesORgxPZl+/TFexb/Qu8
DUGiJ56rZDunZ/NQIutdRZuLmKJyw9HTDqnbvJROUKNoTp26YAZIV38mFuvvh6DKYrEMvpXIjtV5
9pp2iNiIBDvk8iInJ3K+oo123uEsc5X5HBuLeAG+JVTh2+iKVVuDbJIrttrzrE72EbnaHySyVI+k
sQlJW3tQJjvJRXwWFXVWk0f0MB6KNL5cDMVySVmwuHzTg3/RJT6UnksspDuTst0jV9cEPXQSD53E
Qyc56oER+nRTCFQ7iQX6lrNjsiPYTpMe8SrHIZRfw1F99rVR6Dv1vvOYnIGAyy26Gc5kNBsZrtrr
8zKc3qAzFBkEg4Yrs5XaGK7cUeFwOliOARY0wHIBaaPEcBssngzx80gqS+wZqNUicRurMuA11GSI
w4Y9CbCnHqOUBNbaSTICI1DKGxkMfA3+QsHmJvqU7Tatmd7TR89ZzHabrbGhuamZvdbqGX1lb+b1
9k1uKdw4mx2/u7lz5Y5G5y9vkcp9FaWmlvqG8gDHvPVrZfjFXQfT0ZELb/xh+sIbPz114x4cbDuz
xeXw5pb/uTKXeXyzq2WMZskLuB0O4FO1k+/eJEa4DCEiwJtTnm/yR3kGsEilEh4+w28cG7yJnw6f
kjKU2BhGNpoEohV4AwpFYAC/IGSz0bjTdNT0gYk1Y2qXO4w/x6JGYH5JHIwdPlH30jzupHR6a8K8
nKa7qcPa+mBhCR5IkJYwDS2l6GtjmTvU2IDZbwn6aQxqfMxrtq6EuNxU/dSOCusWV+N2K/xbO/T5
u9+JbfL5artOMLf2P+Z2Vc9TjxrQox+hR5Xkr3L1KeZ95j2WrTGcZxmdXqcHonVaL9qu2hhbJYNr
0umFyjz0TVkfsyt2xp4HzxWwCjRd9MVBIc9WXzVqwYBbZ1F2Eq1Zy2jvWX9rqoRblVBZscEEcAsA
yquuQxLOEZqu8+kR88P0SGJxOT1POjoW6OkqlwiyrbhDkO1GJOUmJMWtav5hEDp71/IVEWqeIkjl
TrPKr1RaOlTsPJ4LFmsr4JW2tFpb8db8ET0oSNrtDhFrKKjGSk0g3Mw8B26MYXMju3Ppj3D0x8/v
f/VJX9O9c4fe6dsxsPIe+Ia3BTzVNrgG9ecOn3m1eCbf9/b2idPTK9esUozG0b36J/ZFjKNEfiOL
vMluGpKOSRNlE7bXSs7bfmZ9y3a9RF9X2VHJlAqQh/NyESFmWsO69fiR0Yc1r5u5g9XOx6SCCOhO
sSWoxtVahpz5eEo2aiuKSSl+VF51AWh11+E80UPF1IZCmPEw+A/VZR/bxHnH8eflzr6z7+yLY8fn
cxLH55c4OSdOfEkTE2MfEKQkBTUaZW3auoWwslK0QsIYLe+MjgBdyypoC6EdVAKKOqquBRKvUZUW
UAetKENDa7emb1pUtG4Wk5ayaSLHnscOlP3heyz7uce+3/P9/L7fZ7Tsj6BOqkN1tDGUOb3QqzQ4
q2E1bQ/VvvgdNddIzQdIl5gq5KSp6bJUwqcU0kDOZpWCpknTk9KkK5XIFVypUrlgawbdWS3S+ay0
ZCCo1pb6bJE40n2jMDF4v/HUA7/sj3R9vfvZ0cUPrt1gXjTNE/ek5mrBKuns4p7H30PHQ8HU2vSi
dfvE146fWHP3M62p1zZfMT9JxbKNcxzcobUP7LpKCqMTXb5B6mkDIjhgyFkR6hBiwCArb2M5UQAM
J4p2ex4+ZEgAuskW2AG0cnYRMmAM3iDGZUOSIXCQ5QQRkEMG4sYwTxa2wiWGnGCyDHIyAQYxihPQ
EgGfo9RBJwl1udzCqXSRuCwxsutpIh4qJFdqqFFjNknnnE5nqTblUC/TPSFibcG2YJmOnl6/caNZ
MD1L4W54E6+48dIl8w+w6RLyEoXMJ45wkl0AVNhrNDoskLf5bDEQw4zb5vF7KnG7pdsyymI7CxW/
rZKpksi1ioEKg3HpKVXylCrp/hCoUtEA+FMuwEAmD6+NuGrwOEZkonqSGKxCToKGzVkeKEflE4KI
8uj8SXiZA2PIAlRQBb8zFIPr5Q5zmFPC0uU9KlRpDVRfqFSDKeIik0QkBWlSmiJgFnIF4uQUPsON
DYIYNghvmBKKKatF4syBIpwMUS2ZwcxAycxAWhzJVDq+7RaKt2h9hRy9yahW6aIqXVSli6p0UdUg
01TDZS/N1fqG2EaNFB+Uubx0O7xEn2AgBwdzAzCIg1bGS6XJhG6pkviCt6TLcFC1wna04dHpb3XY
986B50xz+FhfZo5W27t0djxQ+4M15mFzyn8Xu8A0h8RD289uurYtE2/X5tZ01kvCk/f+doIeNxeQ
/TtT7P21hHHejeHyip9VIFv+5n8Mj8vdUo/Dnt97cJZjVVkOsHzU8y76kJwcXyBBiofDp6NRCbAB
YvSnJFGdEPLw65NAqZPz6MJppxJQkELBtbvpRrh9sVsbQTgtELdeeJ0mD9L+EwWpMFnUIlVk0Ywb
/RFbeTha6a/yI4sr4ohGbGo/rC5T+kGNk7wL2aP90F8e6AdBkVzALWPV6rVt20COeEkOehzIelfb
DN402RDkXWFo8bhdpSJK1F/xmdOfbQnFq+bM3f/REx+u2XRl3Wdwr3mBa20MNjR2zdO6Y+xjlY3P
XzpQzbs/H9/x1fpdkDs4CXf9bfqJ3cZu02yJrDwC3Ss6Z2i4RGiwgRcNO+B9LLJwBG1bHv7acJaA
tkGAeSvkrNRPBFcNGkcIIAkhRGQ+wvMcAwRLHn1k2HhF+JUVWq/bv/sdfJ765jc5WjNqKWliGiXh
IqoxRDWGqMbQbeFOukpyGirK61agZCFRjcUaKg9CuBIOmFePLpoVjfbjmJmqZB7RqhfBo//dT9Nx
F3mSPLuM6CIMkrDLiGGBKS8T3OXzhceiT0WtEdjm/WFyHbMdPe0bFg+GXxdfD+e5EbfwlgXNu5ck
NR57nPXNql+IyEBo0enABBoDpWTYSIa3LGIxet0Wvt9IaCALWgS8SOiNLBPWCNsBGxFEMSmHw0Bw
ypFmFXj8EZm0SYsrCcNhGjc8YtJNpsAwVpNis1MMwyRjueNn3raI/hkv9+cxMKo8Tc0TBu7FhzHG
Skspdk44m+oNXmyppzMce3jIU8HyPp0KlsbPgkZ9hfSOqWmt+K9Lf7roxqkhR6M25Nh0m+Hih66U
1SGlhxzSuXPEbXJ9BGsywIrvM3Zb9PtAb72V84k2K7CFRD6Pe8Z/0Dt7Vv37yoWJLfteffDqhTOX
B85Gwu31PfMeXtEQEN01TX2J7h8hc8XptUf++sGenxzp3PDyj3deGt26ZC+X3Njz8/mtS7u6XzHP
V3pDO7of3tK+MneGUJ8luztazPEx8J7ht2EF12O8nz/O5/nzAtPJsd4Qy3kDtXCsSDoHh0/W1gJa
VkNwskD0XgY+yYd8lG5XuVIfmrBfhrRm0Fd3G/KpIuMzIagE+f8znlSivCsYEaNlEb9SqVQp2BKJ
1jhC/aBa8vXDKE/eqUKgHyoucgnbau/gvJ68KOgw5yVW3maZKSqtp8vjRgwsFrSUnz0SxT177OqQ
P3Nf0/DFVR+vWndl80XzcVhnq5cTvliysnau1l1bWRnd95fnanxfvL/jyw07TfPon8wnC2jn6sUj
r9xXV6F1HDP/TjAn9Xvo5r/wF/gsaAZp1GN4LJKUYmqkVNJId7Y807rXerAVZ4jojKV3t46k4Gbr
sYYT6dGGDxo+DX7S8GnrNw18q3W+tae8x9vder93OfcCONh6FI7AEU7QrXBr5gAz3PByMwMyvZll
FUsyg94XPW/Co7PG4VcZG1fRm/lpB+7ikMflQR30V855U9c6YFLnyPFPi8e0eESL16X13+hjOmb0
2fpCfZP+rH5If0N/V/9Y/1wv6PbVOtQ73FyQe5RbyzGI6+AWcOu5Xdwh7hh3nvszx9s5P7eaw24X
h2UxGtDIinXLEx1dKPkSyCUSSDbqtBanHJAfkVfJh+Q35XHZ+qX8D/mGjGXZcEgtMgpYkd0ZD8QT
8WyciXfWzXNGAhEU+RaABJ/lt/DjPFNDBgR4iRxH83DMkIzM1gwyMksyKHPcAz0UXCPWG8ve9EO/
BtqkNtSWZI1QpGUV+08WNbEG28suYRnWN7t9sZyHzb+gwssNEH8ZmBrQ3s9JuQFy0Bik7fL6ZI7I
0JXSEuR7KS1NETVK01OTRJPeVG5g0EUvM5GIhGpOSjvSaeojg6WOdkqQq2QEKMhUue2zKkM2CTPO
SFU0GLFHU1FHdVn1/8iuttgorjM8Z2Z39jKzOxfPevbmmd2d2Rmvh7W99iy+wh4gYAzGMWpLAmiL
G0RULm1sWtGYqF1TSBRFEX5pgioeSlFbJFIJqybUbR9iCTUJFVJMqyZp81Ck8kAimVZqi6pWNv3P
zBKgedjznTk6e3bn///zfd9P8bmIhgrGINOnUWI2pqFoAYb+wJDWrFxx2Nd9qN1Tp9Dx6ToFH+hE
KdKMFptFXKz6TQ+QgPqIL3z1T3jtUU+f6lW8LbH+rt4eevStVyeOLKKqits3daSz1uhQ7SvHb37z
5fNqPKrE0hmt5+hTE/uiM0N2PlXuee3c4aePvnX2q0f6Sm1yMqE77ZWtY73bT2+b3txxbu0NnBeL
yR1bdr6BBkZ2r+/rNDKk7p0HdwIZ0DdwC2g3FuRtYUoVVRolU5KpQ+d0D2cM6wwT0iyOix8XBJFT
oSMgRiyUlkvEJO2sEsD9QxvcidJyie4u4dJEaap0oTRfWiqFSvE4JaR0YJYOScYi6haxOCEuicti
UEy1j08TNq77lkwEUk/layIh92TOw1+oOhG/vcTlDnSJ9eOO420t+VtLza2lx7beX6mTDnRYvENY
3WGAs4dRvclOxUAsWDQtwk00G7FyxWKgYKM2PqVRsbgehbnBWjZKxzSNyoc1+4kcd5Acb3kWG98N
TkWmcg3zzfCl4M/CvwyEvx9+OUI3Ao1oQ28U3wyeM1lw3dP1vUhq9m1+akOGBAxm2VUkKX4z0tQI
dOXE65OXJ0/ePD12YuB8IRR1etEZNjo21DtaWW9v3hMcW109Ob386g//c7p7/aHAT3e3ZDN0cfUn
a5MNY2h08Oe3P5oYJNl8GlSgDiyWoHKoip9l5Z1KXXlB+XriUHJGCRWjl+h36RvSLfoW83Hs48Q/
mH/Hoo2Eb6r3MM8zLxS+wzQKp5lX4p/F7iYiHeEHrSgciTikL8mBCa8Hc60U2ta6iNqvZqyWUHAR
aQs8F2klBcD1pGqtOFVwWw9T8HwNHsEgUZ5Sx12COClVqXRXoVY4UPhbIVDIlQSkIxr1eBmH/R5q
so9Wt0sQ83zcXRaRmMr3n/VkqE5yQURoXKzfdxzCDY4z7Gn4P1eHCRHU7yDxxrSXcrjCbcWkmlJp
NivrGpVWWqHZlDIaUhMwUJ72gMFEdYeYdLDovhv3byOx6DJkMOQ+1J0EU199ENm39WvDz/UXxhZn
lo/uWb189tY9o5gw3PwQ+tevj31pyzOt509dOPXOZyjx6cUfv6jLvXvPG5CdDkiRETxGcVSW+gS3
arOSWhMkSqayuiTKYpZVTV2GK3e1EDN1iUyMpKlnf4PuUQbFQigkd717hUUsphCfZWUpGiEBysKq
z7iYKfG8ENNjdKwjqWI4XiUXY7BKYCFnuB62qB7irnK3O6+iORV5V159CWsTGq1rk9oFbV4LdGk1
bQ4mS9ptjW0bX4KLCnwKPee0x3bkRgLlQtjIZYPWiyySe4Yc1POI4lqA3NREvgqmvSq5pPStTfv2
Y7xv383OLWuhjZrSuTl4zFvAeP/a0GrmYF/ANOmCepAuwLQIJeRA3EzgKBGcTVYmUZuU0byMwLaw
lKgHRVBrljN11osdMvWgFzve1EVCYK0GfJMNRim/2jp4jkSG8yNDYKHsulwzQgSxASGa59AchyhO
5GjuJV2+IM/LTJdck+fkJfm2HJTJ/orrErxW7nQlL0COU59+IkJecB4GBtbRF8Kx8CgMY/898fnL
M+8/R14e3n4bRQX64E47dOBXUAV33+YGIiwqe5y7szpRRsFgkC2yzJ/oD5k/ppkEWw1uo5kP0V8y
tCzEqTzl6HExLzpXhHeEMMpkFVMXFulPsFSwTD1vFKKmHjeMrKnnFuk/44Rhm7pjGPlcThDi0dTz
QSYQyiyiAwvLCKHFB2/jPckqmgFeZKM6uOqORELB+U01BW+oCgrKKR8otIK3jrgK3lJV8MAgTKrr
YeiuwOCUYbDbYSiYMGg6DKLkigpSiFsQ9PJ8me4qT5XpMt5YJe+4ACd4CId4COd4uK7TRzjNQzjL
i4kAXFbOCpROLpxtW2QtDn/w7xbqspasZYshSwt9g66HXRUPcaTNdK3UuvFTvtMliXSGd4mkyJvy
7hDn4TiPniDDop9i+ML0Sm14GD5AP74fYMQ40R1PrXLwQzJXy3k/pPA1AcPgPbVAcyeQNk/AKQEG
6PoEUph5pfbwh0ifcZwwE4gfeAqUeMw2PFZKhJ6+UFzXt58Z2/+iItob1+yqKspOes8Ou7pmD6Uk
eyNzaWZ85NDOgYtrPzhWDZlmqJg6iC58azj/0hp3uB8W2FzrMVo84oaLRFt2kA4D6jBG5dGXcfK9
NLJ5JD8TjlsxRIVUKxQJc2044MUbuDyALbCTARRIG75L8GDEh5oHCwMbXILYbHfcJWPZoCkDG5MG
mYIn/JFBG4Ksy7SMlznENTXCQzia4DWQBi5VgDNmr9rVfvASD5O3a6U+TujKi+B9SNWuFcpP0PCK
pwtPIbBDdFHXchrNKi2JFpplrUw2nU1lGVaIyTa8ZZuGWiOyRiVDbTaS+LiNNCauoZaoqlHZoGpT
zqPWpYOYA/AGlXY0gEbRqDjDB6fYBt8Qp1Kz7Bw/J86m3qff1aON0FRsSmgk50KzsVlhLhkGp1Cf
3otAfDynEALipEF11ALr2UDiDCGhJJ8WWjv5+28cOvnRH+58+kHvqBrntneWNTumWMU0c/17d197
75WLqP36DeSM7Prr747WR3akChsOoPzlRluCZNBe2xGAjVSB6kLfxim5KyywVIiSdFYMiRLb0mWA
rph6iJAmR3iU/a3RVCJwgeUzakiSQXWgo9M5NhQXS6iEM2m54ueXwAKYQIK4G27hRGW5QndXcGWi
MlUJVOQm/cZkzKNuHvMT/BK/zAf5VPcTLpD3rR3ftHb8/7nAcc8E+i6w4m+tNLdWHneBu3wbuOKr
E7mQxAh+bgVz1rqklio6VptlF9clSzayNBg60mUbtWeLnvFDD3095HXof+xXa2wU1xW+d2Zndu3Z
nZndndnH7O7Mvh8e7LXNGLxgs+PYGArYmDzcuMnitIgakbQB1AYBbVwFUhI1ITQCJxRFTduIl9TS
4AIuqlSIUpr8KmpTpQ8psiI3lYBFIbiPSPHSc2cMJGrV/KgqtdKu9N1z7+69d+/MOfc730mb5RVG
ijTjoXF1PDu+wPEVaTy8Jfa11JbcuP6k9ExqQnohdEg9lDycPiIdT55In5F+lvb1yZgIiwrsN5Kx
lP7Hb2hChu4diQjlreVvWxU68clga//cFSs74KfaFn5meOz4/Q/8cPNAb/vi4S8sShmlrLmxZ7T2
ykojlMlQieBD9B9Jzty1Ml584k979l3ZlVRe2Vm69+oHI0ufJ7lkNUL0lyECCjhnNnJZrsRJbtG+
UkDIYP88GdEMfT63gf3GKa3DGsZU+2tBtKyZkwKGqOMJbr9OcWGP1xBiSEUFLSaqYoHFciAYRMnv
a6qVkoMXtZiVklNprUCiKZZqbBdMtQsYL7q4LIyRJIMKrBprFCqo8RweRQ48ena/85Jz2klDPJ4z
OVQQghqolKZU0o63pJUNDMOykbhlTckXMM4n8ZYkRkkxSSX/0DR4nxVbdk6GAJqdrVSr4oytWoAN
dJ0Eh9MKDhIbSMfz+VvXSQzYdGvrGVsDEhUYJDfT4lriSFvTv1l5pqezt6elY9DZ6IkpBTmOne5i
Z83Zrbsas6300be+Pbq83Luqz8EGkuXPf/XtzpIYCdPpNFPaSTFDgajCELWz7uYM9Rb4qJ3aaz7I
tcpi2SF6CpIYKzhYKSBdzFzM/l68LH4oOgtipqlTXNS0lzuYOpg+zv0gNcX9JMUxbsbjKsjuFdxq
N2typpvytWvoMKVhTPIONjlf+bskmePlph8d9hXhC6N4Qw9p4cMRTVEIscKU/QpWpvDDZip8OHDD
52OyutOnZn3c/D02fbKBH/ChhJigEpb+5wTDHiV5Mm4BstZ4zCuCgYvGWmPUeNQYN04arOETXJqL
cpmwwO4llUL+VsmQx3krTQK158MLCacTSgeRPwMSkzDEaVccsqSLTArCApcpJcquLjkFTSADQzj6
fOIkGeCv24D65xcm4vD4cNZpswF2SKyH1eTkk7CBZWEPy8I2xJ66vZM+MmPtYIaxmQ/BG4x6oREj
0PBBaDwBe+IIFCHkj1RVFcrq1M13J92SbWEGsadgujXRmvdTxICe8sFcRoWJjAqzGOnWFPEqUddY
rM5WkXiVEJ4pFM1Gb7loNgjQwLOQaWSSPYv8c6YZjgb3+NKkbeFRQVdkmkFhwOg3ZgN0Ms0gOjJT
N69PAleCnTlLaDYKRIpuq5sRBOWTxVtAXNifIvLCSkeO20wFVyFFL7Sq2A6SnEitBFfFrp6oA0Ky
e3dPYYkUx9nK4L7h3i0qlwgkxGTzS/2t3V2bDjXfdfDZNSsiXl8gRF+oXdi3aXE6Ei788lvDgxND
TVw7HtqzZ2lTa/+KzZ13b3jkZEYQIDmh7M0b1IRjDoXRiyb/HPecm7Iazo3CU/gMuMchSbS8m8Js
nGvlTI7mtjVs5DmKnsK8GWO4M24lgh0OJDAaQzFN/oC8Q5L8Jrx8P4knMZY0iv7z/kt+2h9WCHPY
5SYIwVlL64G4GxQhtcAQledmKuWuuS6r4uyCghMU/la0FXsXyimL59uhhrRIo8ObAp5YjKfeeUfI
ij1L1HVnRnZ5G3c+/updjrnaiQ1zP19XjG0InN/QnZzAH6ZGXt9BuNoPeusafRRF8R5T8VGIwj7k
w45WdSQ4EhpSz7qn1fdVp0o42tOhkuNno5pRDqwNDLO0k3dpTkcQByMhLYhYkaVYzGhsQJS1wNTN
p83NAorGI9FovyBKgiBihNYLPPT4KI+RgxXjECIiuS6toilSYiQoRESBx0wUaM/pZNko4iJ/E3e0
CqYwJNBChb+MTVhiEUwcv4wpQhK/wjQeIieb7FprWCeMpHKGanoEQ7SqzGnVIar4x/AcVAwyBT2Z
uADvXLd12+xWePNz4dnKbKhqsTWR1r5gCXt9pRL8BN29LTr/dfH1vUxLyOroISRWsXjebiufNKQy
1StEkJuySg6rksNSojdaxqQB0po+JZUsIxPz91OcUMa3LgSDSYxDwoYMABfB77eiHsYs68T4Su0X
pXiwGV8vekMLvrOro7mE2xd0dtbeiFK/3Z1SGjIZb0DNfLH2PVx8YpGWozIZdtGeuSTxs7fWT1fB
z0W84bTg0TyUm1zbH/nlZQ4s4VVolWelMqJ8LnJ/y2Zlc2RTy9ORqcgbET7vz0udqFPpR/2eMXbM
OeZ+sXgMHVPeDntgV0/R4y7yrNupsXI4oMkigxns0IBd/JrUJOfyaZ0vFvuVsKQoYbfHEwLq8axH
WEIeHmGcKCph3uNGTjlXRGnShSpTSV/W96tC+rIqS8ABDKsg7qG26bb322hL83mkvNEWDCqCXJQp
GdxpBplCIZ4zcn05OvdmQkfMJbh14da2O64enK0MzM5VZuByDS7f2Peevu22qwfEarla9YKbweGY
WF9pr6tFt13Oz7sc2T+W/pXn7dbpErtcXeD9SkVHFXDjvNf+yYkUkd42iUF5FbSFN/6g9uu+nhZ8
vS3f/vKXlrYtw6WWJX21v2xsW77pnrEVRns3xi6XEIrkF2Wp0y+t5EGHJUPZLbXnceSFpZkF4Gmm
+9W51bWPuu4d7V2yxuzNclysaYJ4fgB/k3qKfg1xKGv62QPI6YG3Rx9oAIdUE48+S17PRwNz5L1c
Q+UBqFvwLSECh8QPbz9y9LHtR4/Qrx3d/tixY9BFtz+P/Ae4ZgMvs0FLgPcQYloQYh9HyDmEUIOI
UON6hLg8Qh4WIb7/fxteeA6/+w6kE5+E/O4dBKZthDchFGlCKLbAhnoJocRVhJK/s5E+fwfZc/8/
yPF11FFHHXXUUUcdddRRRx111FFHHXXU8d8FohBG5CMhmvSwAmDRp37oj/UF5EV+SQ4EQ2ElEv30
tdanbzlCK8GuQWgtWnf3Pei+4c+iEYQe/Ddr/rF2Is2mBmBhmAAk5RgEgF7lY1Bg0GHQY7BkSGJI
ZchkyGEoYChhKGOoZJiqoPT/P1AdRN6AIREqn8dQhJD//xgH/PQgFRr6+AAzQRUcDGlQc5gZJIEk
I9QHkkAIYbMBWUagGGbhBIoYMXhD2UxAv9VC2cxA8W4omwXI3gtlswHZ730CnDxcA7RDMnNTi/1S
y4PycxPzdJzyc1JIlwBGeQCDEzDyXYG0NkMIMMBygcFWzOAHJMsZghjygfxEYBDqAFXlAwMzBSiW
ypDOUApkJwIDlnT99NABCmlWDYZPDDZAxazAkBVg0GcIZWBgbwemEGYgHxiojBOAMhwsQBaIB6MZ
0piEgNrhAD167YGAwQGYxqZygIw5w2HKXAyNZaZn6R4zknzi+W2+ckhygFUvemzqBqK3nlwl/7vz
b4+AK4cpkAuKd7DJABBvKHQKZW5kc3RyZWFtDWVuZG9iag0yOCAwIG9iag08PCAvRmlsdGVyIC9G
bGF0ZURlY29kZSAvTGVuZ3RoIDEwNzUxIC9MZW5ndGgxIDE5ODc2ID4+IA1zdHJlYW0NCkiJXFYL
dI1XFv72Pv9/b5oQ0eB6hNy4eRCJN/GICLlXQqTeq4mqyRV5FCFaNFFRagYRRZV4VTvaaalHc4N4
tR0Zj6HUMmoQxlJmhlKlaJElyT2zcztrVjt3r7PWPuff55xv7/3tfS4IQGMsgMLIEWO6dJ+Ukb4a
SAuR1Rey8t0FmW88sQFD/wbQtKw5s+za+eE6+XYVsBbmFOTm0/jPxd5vLGCeyZ1WlNNv6pj5QNQX
QHBmXrZ78vFma/zkvGmyp3eeLDQqtr4KBIbLPDwvf1Zh03WZs2WeIsMzbUaWG4Nebg30l/sD9+a7
Cwv8rtByYHid2Nunu/Oz3+il9wKpEwTP5oIZr83SP8sXpMY3fC94NbugqHXyUSCkBvA/aq4QVMMR
KiNEzURLQN+QcbtheIfpOnMqHN48/U+VILvX/nf88ovANqygABTjLbjQHX/CKUxFAUahHPF4QJeQ
DEOsXkdHJKIeLciNIRQnsxWw6VPy5SV9h2+BsQEL8QizcRFZ+Css2Eg9EI4++BoDdC6CzWr0xmKs
1f+A1eiJj1Gtr2ovUvAhqimexqgFZgJexFzMw3KyUTT1oXmIFAyF+BJVHPRcJRohDS9gLNKRi70G
yZ0mRqKcLqgkuSkdpdSLqvRO2AVVJGIxiHpzJ30I7RCNnuiPgfgD1mA9LlFnGqC6GQdhE5/cOEiB
1ILa02H9HkJF0jBBkC5HGbbjNE5TKI3lLirT/NR7G4GYIQiLUYoLeEj+9CIV8gG1yztQT9F79DHZ
HSf3ODFMcBdjnXi3FftQhb9ITKqpLY2kdXTfmGV2r1/oPee9rlvoh2giWMchD9PxJkokN+/jCK7g
36ghg/yoKR3hrnxFBRrvmzYNvaSBAeiCQRKtQizBUpGDsuM42akD9aBZdJEDuQlP4/m8g39QJapC
/cv4TifpbfqoxPwOrHCIRGK0ZLVYsrZScrcTn6ESB3AS3+MBfpZITqFSqqBKesrNeBdfMOrMavOB
3qzrECDRjkAMuor0kAgmY6hgmY6NkqmvcEZq5hmeURvqS/NpCS2jFbSWyuhbesKL+SxfU2XqU+VR
Jw0yuhtTzFLzumWU1e0t827UqeJdsJzdU3iTIDHMFi6+Jpx4T+K4G/txWLA9Ra3EJVi8Daf+NJoK
aR4tpJX0R7rMKTyFZ3CBItVWOVSUWmqEGjuMc8YVc65Z6o30ZujOaOCNv7Chv+BOF/kdcuSWuSKl
EodyfCHZOiGsvSNsfoxauY0lzwHUnMIoilwi4yTr6TSR3JRHxfQR7aArdJ+DuCW355W8hj/ib/g7
NVO9qzapPeq88hraDDC7i6SaGeLvDvORZZylxDrYOsm61e/r+uj6k/XXvI28zb1R3jHe33s/1+l6
jn5db9Fb9S5drqt8laqEu22FX3aRKHSWyknFcEwU/FMxUzi5DKvwjshW8WEP9uKYMO4cvsE1fCty
C7cls3d9Pj1GnfjUkhzUTfgSRxNoEuVQAc31yVu0njbQJvLQYaqiU3SeLlE1XRd5Qk+php/nYO7C
cezkZB7BozmLs7mA3+T1vIk/4f18iI9Lli/yJb7JXhUimXCpFPWymigRKVIL1Ra1X/1dXVDV6oaq
kdgYkqMww2FEGP2MXGORcd3sIHGabE4xPxA5YgmwTLGUW/ZYTltuWy3WDtYU60jrJ9bdVi2VUo7V
UqW/+gnjtlFHfklQKjrKe+ldOsO7jXscSBk0V4FjjRjheBpucYmKoARVSG2kjt/GUFYSw0DezMkI
9x01Wqq4h/BwrHneaE5bAV5MedJvzgp/UsVmKQ4hQlejKd7RU1FJNqmobL1BamEBpVKV1FAuz+Tv
jToVJAy9oS4Lb25J7fekMstpTOBOwrYB+AAt0FfyeQ1FZOfOGI8NaqlkOgytEG1MM6WH0yO1G9u5
jEt4r/6KgR+k7403kgnGden70Qilu/hMsJ3i81xClYaFttAIwRCi/IQfJxDOm5GtZpPBC/gnoxqX
uS+PVzH0yOim5DWUPC1CBt0lP+ykMq6hMKylBeL9TbrLNzELP5HmerWS8+gknaAW3IkGq67w8g2a
JGjCcd+0kR/HSR1ZhFe3eLvKoU04bx5RV400tQ8G/ZniuE7Z2Ulpqo++hwhLjWrsvaCT4GStVxsB
9T9KdGbisj6mYg23May2svYs22i1yjfT9SNvsbmIE5Bj3rEOQBEnSYc4K29ROaLpR24tcQ+VlX4S
KZuxqraWR6EtP6DHKKSVUh3h4slY6RzlyKVtYmvK2zRQXoFnvEO6ZpqaLX1mH44J2+dJbw/mLHln
8mg0WF4Jw/cebBQ2PDReQZH8exiJL+U13SFaO/PjxEFjEwcmDIjv369vn7hePXt079a1S+fYmE7R
HTtERUaEO9qH2UPbtQ1p07pVS1uL5s2Cn28a1CSwcaMA/+f8rBbTUEyIcTmGZNo9kZkeI9KRkhLb
MHe4ZcH9q4VMj12WhvzWxmPP9JnZf2uZKJY5/2eZ+Itl4v8sKcgej/jYGLvLYfeccTrsB2j8qHTR
33Y6Muyeez49zaev8umNRQ8Lkw12V8s8p91DmXaXZ8icvGWuTKccVxHgn+RIyvaPjUGFf4CoAaJ5
bI6CCrIlkE9hm6tfBcOvsYDytHY4XZ5WDmcDAo+KcLkne0aOSnc524SFZcTGeCgpyzHJA8dgT5NO
PhMk+a7xWJI8Vt819lcavEGpvSKmatnyA0H/ob1qgKOqrvB57763u2KAUP4TgY1rQiWkIU2BEKEs
P0mBqAgkcZNGugmBIkGD0orQRtMihVn+ESwIOGjRdhLtbCIjGywxgCTQNlCwkRksTDvQUUoDlAEq
Nub2O3ffW3aDrdiZZvLtufec+3Puvd895z4q86fGlXvKS0t8QVFaxHP0SsW8k4P9l50fcKuKwb82
ybcy2pooAjkDHndzNRBY6Q7umuGLtibxb1ERxkBfPTnXH8jF1Gt4EwekwxF2n5cSXtRcTw5r/Avc
wbs8Ez3zAwv8OI+EQJBmLk2qT0jwNsg/U0KOO5Dv8yQFxyd6ikon31PXhwIzl7490OseGGtJG14X
3yu8m3U9elqFuO7RhbkRmyqp5lzKmxnZTo098kwFC4LuOW544vNgIVn8MzeLAnOy0Ax/RRp6Bctx
DI8H75rkD8Rns577B83keI87cJ1w7J72v8dqSi2NIzn+OnGRyRHhF+x2OZiaGhw2jHnhnISDhI/f
VvWRacOfCemXPIvi3RDYPnrEh25F2enY86QkPtXVIS+VoRKsnuEL191UllhP3vTUoqDuZ0uTbelb
wJZq2xLp7veAvnuIvwL6Bl0pkf+e8f1658zPDmr9/ot5btieN8uTN6PY584J+K29zcuPqYXtWRGb
VQr2nuQTibpV0hOFsoKJJZHGXPHFBY1k/DsUk8tDTheoqDSaOzcY758S/i3qlpR0h51C8gr3UuJW
N8vNYHZqbP2BmHqMe3EBAYeNFD0vvzgQ6BZjy0XYCQRyPe7cgD9QGpLVZR53vCfQgDdeMLAox2+f
aEjuW50YzF1ThEXM17LBVp0m1nm0VTPqvNqqWcW+hni8bFfl++p1TZ/kn1hUdx9svgY3kVdp9YiW
a26uUZ4GptfrLmVKbPASVSuroRSqPiekkdK5bJ1Gc0J6WBevdPhLU88HfO0ldebQo66KDrOj03UD
31LO6PeFeNMxRuNvRjwCLNTQy6JESzGIXgQKHTW0wTGGyrR3tO6wrdFrZJJB2r3mPGrUSV6EbhT6
5ehj5LtovwyoAtzAZMALTAV+AnwCPAw8gD7LgPswxkvAEZbQNztLqNQ4J3cAJ8xCCpgt8hDKJ4Fj
ZgutQ/23mL9JrJX7zEJ51FgsGx01cj/KLbAvQ7vjkDzGCYzXw1hM61E/bZzTCOu4Cf0S6ELo1yEG
UXd9DJ0Wg2Sm8FOWQfKyXqPNR78RwCixlnU0FNKrj+ncDvtR1O9HHx/qu6Dvg/J0jO/hdsBYtBkM
mYaxh2HcdtjzWY+2w7EeD/wOASWwtYhMWqtnUrvIlN838qmPte5XeN28ZntNyv+wT7cB4/LY3miE
/buFW759Kc7Apz9CPg1kYC0deiu9ZaTTQoM69zr60GqG8xTOvUbbBsQZ5TTQOUhuho9TzD00EnXG
bKAY/a8aO+RJcY28sKU6XqJN0E/RM8CxkVSv/4jOO5Lpu1hvGuYzmSfYtw2KC+Vq33TIwcZf5fso
cz3ZOUjrZu3TDt4b51pKQ/9RmOsS/Gg3FmsB4IfwrR7YyP5g/nTsuR/nvlcr7KzFOL3AvR8A38C6
qsKQ58DhjdBNQLvBLqLnrXlORsmTzL1oWOdj47QNtfc1eFHWUDNwA76kAAeAKvT7CDId+ochZ4KL
zWifyXwFL66EuSnfYm6A73+AfjT7rtYAfjPHwvdGW6bPo18AlcALDqJXLfwUbdR9Yc6yn9bY7cwt
5owtLW4c1mvxjud1Mq8sqe7eWRqqfMDamVsRiXvH3FfyAu40yy00lTnLY0Zki4oHY/k+4mxTItLy
h+8n4sYZJS9QocX1sba09uJQRK6V78BW5ehPO41McD+EOzCU+omriEFnsIdP0DS+x8YWellfQX2c
FykdZzkdY23rIrcynG3aAozXhP1sNlppG+RWo02/12jTTLNWXjDatSazVn+Oy7fLrrDbsmRE276q
/n+B/qFZi2+KWvk3s01Ko402Ya3kvKiNANy2hL4eqAaGuVK1ra4KLeQsoHjw5hpQaXgp2/SCc000
3uir4ncy9AUOwv5rlGe8Qou1Jq27KNBSHLW0UBTgjmIu/UNazuDxIRdFeBTmWrYtb+OSJW2+dpFH
OOZz3LWlunuIq5b0xdSz6VucGzg+c37gGM0I81W+FuHlJuSQj27xM5an8mYUP1/EmBldeRklz7Lk
3MLxnXML5p+N+XdirNd5/So+IsZxjOQ4hzv/kN2+q4z0r9H2Iz7sVXG4lYrtew3wPf8EtgetOII4
THtUPKykxxyFVCRG00MqHk2h2eZxcqscZOVUo17+UsUy3Cc7l6o82ibXR/LoIHk1HM/kYRVvDsgG
vp8qbyJ/mru03uZRSlRxZTH9Rt1DvoOfUjbmKhBvIuZ2yCXQZYhxiL3Qi0tUrGynaIhYgn6G3Mw5
UTxBySo/npKVYjyNV31XSK/xKfL2G8gV1niqDaS5BZzEW8DhpwMqFhQzR6iHHY/57J0V8l3nbHnQ
UU7N5iNYTxn9BWtpVXsQks1qH7hvf5nGe+HMlxvEDdmJNr9X4D4VskHtB/Yoei9UbuY3BcZ0VNIW
tR/cZzl97PLJ8wxzPj3j+AzzYC5zHHLJRNloTpQbVWx1IMctxTqHILfF0TjmvfMpKcUQeczOw6KR
kkWVfN1MlLuxd/db+qEc9/lNwu8NfkOYv+bcL0Oqzwm807qRl2EMBS8raJ7YDayknuZuvEVC8gX1
VmijrwtD1ogqvG/C7xN+IxSo+1Ip3zDraRjfMeUD5uC7j/M4hFhaiFgywbla/srQ6Zvg3Ejs93Rg
LpBj1Q9aOBSGdjzcRtNhz9f/Se0ol6D8Pb1R/FhvpNH8DhQfyDbxvDysb5TPiUdpvzgmT+j30Hu6
C368Lz8TH1CRdpmaRTUdEFPxblpELeKIPC8OybP63TRNHyt3ijqqEMtlq3iaposnMd4GOix+Lq+I
dXK92AKOXqeD4ndyhZFF7xl3Y6yz1Kz9jLbr/6DtjgcpHvNNUONX03qM309hOXiCftFQvtq43ecy
PZniLH+LY/xlX20/bR9t/9Yhl1n+8bp5XNUPbYwpNI1I/glIDsvOGTiTYo7rKmblIPa4EIseo7Gw
JxB9fhXYg/JGtL0BnEf5WSCA8irgX8BrwJNodw3DjASGoP4dI4GeteJMJdqnQrcQQL/PT6I+GOUs
lFuBgUQdH0M+BYxH+SYAfYdpoQDoiT5oJ3muDEt3Ge13AKdRfhVyVljX8TbK3S25D9gMPAeMUO/X
Lu+S/4P8wnx0p7JLHsromlO+ksy5IxmTg+zz/zJp5ZaS26S1D/Y6ovz5TzkvRoI/jdHg2MrxjeMq
xzaOpxxP/s161cdGcVzxmZ2927N9a58Pn+9s45vznXdtbuHs2z1/4A9uz/hMy5VPk8oXCKZtQkNJ
GxrjqFFCDhKQChJFFU1L0xbaiEoIk3i9x8caE6CqVKl/IKr+hxQVlFJKK+WjVRq5De71zZwLbVS1
/3T33vvNzPu992Zm52Z2HyLsqXxfY+cJfICWsXSb7aVsP2N7KdvPXK/y877NdQz2iKOo6Z/9uoy2
wEY/V8xmddMB1BIc7fZl+iw3NKr6/swSModOgUyD3ARhmebg8JlDApkTplEbokCeteubuJdjDw0t
Frp7y4VifIV+O1MJr5gfgAjEIbOovexVbE/oH2aqoAFD2EsIgxD4T1JykRyw+2hNJkiKyEdsFAHZ
CLIH5A6IGzpTRLdBPgApgYjIT87Y7x6mV8kpvBu/DkFOoOMebHppQSy4hIJQIML4nGAhXLqOg3bD
Tt0pXS8+1bgTurkfT7CGt8lBHGT54QlO20nDdAASHIowLRzVtjK2KGVcGuFox8rsBuPHV2BaLJA7
wvQFYpKWZZDoz8U+dVC/Ql5hN+rzoAvUVLYZYQfGue1JILxfVBJGHVTZc9h1lRyAKTnCdTVr69B9
zLZpq+5luH6THmW4Zp1ezUKMGJUAZoW6Rvcrq8c4ydYN5mPHDT+j9gzq/jkIOIiM0kdmQBk0QkrX
Vt2nqCndrcQNL+R3Sn83W5UVhrevw9C/r5xVLiu/VESX0g1WvVdv6FvW19tHQkoQAp5vV3oV8Qo5
wG6keJDpozWUdZ5+gwpVtNOAUf2pSPmw97MbUSAFaM+4NC0J4+5ptxA9B/yKcx2Q+B2z8hyN6tGY
tpkNqWAvMzhE2aQU7HAEov3+Ulgz9DBMBltYhYuf26Dr6nIjU1l6nxQQfPqV5gE1wD+CS58RAc9i
ekQPM+zo0/0sUsLgVViUPL5qiKz62bUphjCRHFqMEIDpbTaiaqeuR1WjF/LPm5UqJK9Qm1r0I1ch
FSYFdiMVBpagPdTd4U67ySlhWrgm3BTEU2SaXCM3ifgssI4RQkkHSZMNZJy4ajJdwnvwcMdBnwK5
DUJQB+g0yLO8Ng1rCKMNoCEiEsA6DVZWSrNVzC3jn7Kw/wcmNrGF9+C24IYoZmMPRp3YxALGqAIL
yIOCQdhi/LUeM1MlvCjEUArJeJDrHq6bzMaUfCwlH0zJT6fkfErekpI/k5KXp+T2lJzxCV0ogmSh
iWn8gOufc72R6+VmY0T+MCJfjcjficgvROSvROQvROTxiDwckTMyXoV7kYwGue7kuplpvHC+Zl0N
qriGF9A6JJMZmNoAokLAVlPUEepsNQ3gscNzNNMguOGVEIPVBTIFIi4iQVRk7Rgl2S6AP0Ex/HnA
t2w1Th38ZhmmWMxMAJ9BKvPCP0VhrACeRlO8/gZKcvzJIv7Ijj0Dbj9kkKnAP4BvDEgCCQye5Hlb
TYD5GTv5HM3U4t2QkzU/jVo5LQtLhGF60S1mh0/SK7gFhQVWRefVF+gC+Cs2/ZvheLBN/9rqCFM2
va86GGq/A9vrNr2bhJpZRX+bvEvfTR6mv1YdAV+kv1Jv0BuKIwLxUpIT31J5kHNhaAT+yeR2+j31
JD1ejn2klZNehcmcMpfQV2BIk7G7dA+EeTL2HN1eDvVEjPfgsXu8Ngr9Adhg8Mb1Kgu8hK5JfpmO
qFN0dfIGXRXbTvsotF+kK1vv0p4Yz5WIcfd4GAYHPVkWm6JtySn6WM8V/Ask4SMgmpmQCtLXpV3S
TiknmVKv1C2tkKJSi1Tn8Xt8nmqP11Pp8XjcHtEDL7OeOqd0x4TXKozq3D4GbpFpkZd9AtOg2JEi
YI8AL37WEpITcqNDVo+Wc6TSZqtXy1kVG7eOzWD8rTzOWde/hHJfjFgfj8YcXLnpccsVG8KWP4dy
W4ZCQLaEbzoYbRlzcIl5HGqy/KvH4MzC5qGjTQzzh47m86j++XQo7V9Vu3Jk+D+oHYtae3SFtH+/
Qs3Wd3OjY9bZ5ryls0KpOZ+z1oxGto3NCvuEF7PDs8JLDPJjs3hE2JfdzNrxyHD+IQ0W1EtAg0X9
UplWQGFGg9Vd4LTtZRoFb6ApDBjtDKKcRvEZRoNlxngzUzQ7PEMp54h70BTnTIl7yhyFc+79C8fl
Q/c4557Lx9MFOaW1FSjJVkaZibYCYaY1ys2bHpljZfO+snkfN3/tkdkom8+WzWfBrP2frqeG/hcj
u2t0COc2js140FB+9bYy1vv2rOLroPbC4P6my3gpuYWqtLxVGRuyqmJDKJ0Oab4B3PGE22u5oU0C
YfT+ltDLTZdFBFPO6F5olhdNKzIrMswEy5mZqqG5ZtEUerm/BZKcWTT5oLkWksA6TozCutydteI7
AGLDeRTK7hqG3yJMwDU5OTkxsXeSXeCgjuaswU2Pj82oatZq2DGc17KhXcN7/8v4Uc6Kg1OaOUlS
1jLBaWJC436aNlkuQGxW/PS1t9zGqUibeNiOWdwJFkXDMKVO6TfF8FJ+6l7QjJCqGbPwVXdgxm8w
ch5P7GXeEKscYaIclf3D2Rcc3HBeSih9XsDzbskRdppLkEucJ6hSEucxavC4XfPw5onXFiveeAee
y8cDCwPrfR8NrFsYQGko+x6ASna21LbUKqBgM0EPIuT6A9OFPkER8TpsJtnSH7APFVEVCs9Ctm/b
7ioIuPdCRYP3q38JaRBtHRzeC8nOHr0+UOeORdWuVPdZrX8gHu/vL/YzDQI9Rp2l++Rn5DBSURe+
ZYYqIp6WLnwQH4y/hk80HY+fSJwzLmpVnTAlZtBblz5dfzopdMfXRgRvtKHLWx1tT1Uz20oopIMb
guNBMtiJvSZUvWZD12z9LfW+SrAgiqi+PqioasAr17d16KpSLyYDy41m1SGvwfy0tUajSGpHokgD
al0goHbAW1gx7E93OCRhyo2NvqpAd7sa8MlHvG/j1UiEkzUA/SeX1DcDJvAC8P5sVv+D7vKPbeI8
4/j7+myffXe+nH0+/7rYcfzj7OSc2HF8Dk4CPghhCSGQEBKUBAu28qNE7UYC1ZRRKqaWRrDSdqRB
WkcJ3YCuAtouWZnLGGyFaeOv7Y9q0/rH1kmZVlRZbCqlmtaYPedzaPfHLL9+7n3v3uTV83ye7/Nc
OJpBAiekBOJlAcPS0YUhRfilYQ4loC10ID/02M2ZjF971i3FMv6jQ8q8/57f4E9nBbeQpdK3QAa5
Ts2BBQhpl6ZO2qaBeF7btJj26tZTnQth3dZU1+EgFcvr85+6cyuIjfbfvS8XJmX5folbflDS/gn3
Kwg3V5Jn2GaZPcLdlj15BHNuCdtzdkfOnoMvggvM3ZnR7ls6Z1ju9u2WFC4gWS5MadQWqunQDulw
EykPP0AZGPGHH6PYw49XwWcUFWRcwARpFpxuV2u6LdvmNutAtLWZSf3K0ZZtTbvcbVDnzAbBWXlM
yUjEr2+5CMrC2ITY2lD3qTWy7BKe/eaWTb0TN2cP7l09KER+o/bsnV+fePLopXXE8eWxcZuVY6yc
f9zz+JNyQ8tA36X1LdMT8/jrE9vUjVO1ncPlhZn1W17/49+GN2nswRGN20wvoiTqwO+rZ8kAdoa8
NXkawKFg0Gq2M0NpP7Qno2RoNd0K07SSESkfvZ/aT/+V+gttzgtbhJ3CcKvxy22h9kxW6Q30dgw3
zyin8Q+drwoX0VVcpN71/yyzqLDbEJYw/lTBjAcepbTnK5tWq1FltRqOwEWt4nQK4Ygk8U9QmKKT
ZWh9PlWleHMq2R92tuZSktieDTsJHsHrI/TKRB0vOXleao0EyVzx4YcLgVxOI5f2eFia74xLPIeK
BLEovc3TGn1UFs6ZPpuhT1Aw/XkWTt51NkMVcZdKEUvJOcRzvIHXAeavAcBZeKNiReBVhEOKqj+S
EWHjQlzRjGoHqu+JWPR28m6+k0q/oWPMPShU4AP0JpeWH8hyCZbv/w98+ZKGn0XHDwNtOYcGn8Zd
7rOS/AX+jLtTAO46Oy1HNPR0micLBY1BeQpPPdLlAsbmKjv/HzE+q5EVk8IhUiEyYFBlCzJuK/+k
1m61OUIDoZ5ZNZQIxL7/7a19myZvnDm8L7tZ+gZNMjVCvVsRN+aeKd9b1/w4bje9+J/duwKUw+bZ
Jex+OpXI7Xr6o5GOmUNzeOvEcKIV74i64j6BtZPR5YPq5vKuG31b8Psadypo3iRong9FUVnN1nB0
1MN5okYE/Z3BMWQZtBri1sboKmtHoIfstfRae6hxy3ZuODpr/JHxAr9gvBrlYprbV0uKNVRrz1tC
DjpvsVqsJhFZrEIQnRBVC7XGJvrFpEiIIh2OOEhTjKaD7TVCnWAQfDHUa4D3VtXNQkjZo/GBPKvC
H5pnMeuV5FueFQXq//fSZoiipualfMmRSxbkUjVKCASCu6OHpIAKFa2yQuWCo1i1Cman8paqJTVr
ZdZo8wWwuiJBxAq8HjItYnqYIq1axSAhbDEIlaYC4ZD5PvnMWM+xZ4XSn069UsSu2Ym967a/eeD2
K4XDh5WWvX/H0+n60SMde/yfFL81h1ddGekY2vTY6gafvaHtB92NmT+Dz8vnyxsMa0wCVKwU+sdV
R1qt4TJpTSrFWMWqfpuy07YzOi6Nx2ZTJl8DTnVLY/FkKtXPoAPmInFGrWdIxsakbHVRyRmNSq5i
KMLVRNWaXLQlLkU56wGiUgMalZcJrBIDhIHYnmaKhLy4RcKQvvPvSoElvt1XJBSVlj5pibqjLVT6
+ZVMebAMylsogdsn5WqGyFBCl1bSA3nyD0qcnhLg9MlqfVCdNjgBq50CBgNDgqE7GH+l+PK4mhKQ
Bu6KhwW3q+J5XncyuBwqsF6YO9rLy93/eiG/tiXodzm8rIFgmMGDTR/Vy/U2u81rElYqePnQF9/9
5wft8bokX8P7eJo0GY37XiXQJOORCIMxrL14gMoSV4D2LH5JtWIPk2uCQWlF+wzvXOMM8TlL0oVE
g5g0DpJbrVsDg8FpfLjpeOBi7Hz8muGaRO/AO+I3MTFmHQuMBYn95v3WicC0dTpwWDKPNA4qT0jE
VqRJt8LDwNjQCGrAO7PdTWNxJZXtRzicwKhpPozDLdAHkCTD1IlBpygGkYyycl2iyZlINCVkykOL
bfGg2JTgnCd4kMJFhowGiziywEQrYrcDxM4wt6DcabqOI0iGFiABq+5cQr9ZMe0Vs9iYyVQsiHll
ubayrPJeX+ZeAie8baI74RbbHsV/Jd+0T39paem+XIJCXanTVbHMd86YdBKACI+sEwEKOoWrcsmt
yOUMxx6BYl3JTNDJvnfSUKCzWr8aDK0aheINeTdZaTsJR1ZPN+IrylkVzC+5gBWSDK9MyRi+fewX
v92RXuv/jsBZGbuSrysMtTdHE6FDLh9fG9t4bjRZlz59NRj2MQHJTBwv57D7nXVK5+7yeC/H8rbG
Ef5YLtYkpZ7Cp/oanV5P0+9fH95zwTA16XbVG80RUMhOYGYRmLEhL7qirrUYrISZIs7zb3nOiQuO
BdcNj3ncM+o9xr/gmeNf81xwkFm+3fs1vte73TLi2MaTFMPYIzRJmEzuiJF2alLnII/2DWXIo13K
S+Q8aSC9PlZbjiEQwTxS4R5SuxQEBR6pAQWhICiFis5BO31L1BWxWs367+rB6r8LogjhqfxoXVFB
c60TsH+kZKTmMr2jcRCL8+Wl549feROLzz136eJ4z+znu3pPfm4YOF3+8PLb35vF8ctvbSg8Vh7/
w859+MegWQ8D5Y3E78ALYZTGQ2rfMD7JvMZcYa7bTDmhD21gNwg9jcPmPexT7LTvcvw9y/WG9xrv
+Niu0AAaYYkUyoRURGBbpCXNssjlc6dcAutMCeFusYjfUNl4KBXuRxGclDASoc89qYa09IgjFoXZ
Op/o9PlEKULRsKvGh32tcdHHJa5BI0sC0M0KqXHdoJtYxahCUCHVOuW/7FdrbBxXFT537uzOPux9
Z3f2OXe93pfXWa+9u47tbuxJcEW2rB0/6rYGnGDSxEllO82DWlSQpLSE1urDokSQPsCIlxSCKhJC
3Kio+UNEyisI/iAQQsJqSyWTgtIK1K6Xc2c2bQMIKRXwA+0dfXfOvTNzd3XOud/57naJqNKIdK+0
LF2UDNIFikqfZr4XjMVWAlxtdBUDXDJzW3WFcBAMF64GUD3kA75A3rJC+757R50W9U1x/6tyh2Ot
qmdt5o86Ox5AAXGDeuDi9fpmuL4bAKdw92i9piJKJU1G6LGSuvX8B4xYUtsD3rwUxbLzTvIX3Ri6
fqqXIYn88Na5b09OHll/6k9dQ7my11cYMq+nLVNbWqs+hYUL8/37CrMzY1vKnbO/7KSPvHxsz2MH
frve6w2tr1d8XsUZj4s9R+nsuCcYkZJV9219B0+8tGtk4q/f5DyZQCf1YrTT8Dd1i4AcGUWMkgm6
w7zDMpY+RU/bT8nfCJg/GzgRqGXoI+JJUYgoCh7Goq+l0jkYIoKHCYpAoh3NpBnrjdriiRuNREoR
fElRWNTDWJQpllSUOXJm1TxipuYLggqKQM+kLzMejayvl6mFzQWmtheZ2opoQSgMJ0LhAjAC7Cvs
RXaFXWU1ZkRufPhchvm6Kjxa1+rhyWRWq6tTPEbvUpYeHZwm2sHiPXSlnSw6c5yTMNTuONWFGi9Q
PCiJpF6a9EtnIW1qhkwuPffEaD6aaJE3+qKiIJmsTnugOD7dFmkzspPPM7snuqGHjvasB0hmYTAZ
31raGFHcRpPJpn78ma3jB31HhLnZrKvJYUbv19ZqrwqvoPdzcF5t7SLE1xJ0DJisol22brD3JQ0p
a8x+ktIOMkC2k51EJCtEVC3ZS5CTDK1pyb9CzqmFDZdknzXc6rQKi3CJqKiERgghl219V9jv2euM
HmVPoP8uMpEtm/oSJwKL/kuyVhYKRVnNIaIthWX5oizIn+q8QAbJ3SBnHG/wLXANy8G1qakq7odV
TYuVVtf0fkrLZi5/aSzBsxSzGCu7Vvg1T8Xcea3Qo+OyQr3+c64XXtkcN+wd6i+HOz9T+c5D23ZE
XRt98c1x48FdlUlH6Gz+sf0sYJtxZsJI4T89fv9gLlrqfnxJ3fvVlqYsGfzSkYn+VEvpV/cUp48b
aLIDM/hO9OEe8QGIEOPzYMACf8Dea0c18nXDVeEtG50ILsKbhLaG++AjNmpnYSYcxUQSImCzE9Eg
SRAORYIkEApHZINfJCbkLL9fFOmTsCwQo9uKpVvx+nGT+r1Kyu91CGU7VahQo4TOMnhOsi/aLhAC
kkDVJpdX7e4tXPRe8QreFXKLalHM6BbFslCpF1zO5lw/2b1qyjPg5erXy1lJE05VlFqrPKNXda7h
LGPQSy76vFriVRlT2adlMupgLYsNpRJxXNYk8RQ/oPACm5di/7K2xjjJCL7hZ53PnA45rP60PB79
6FhPb3sP+9YXLfOf/7D4wPrrA9UzO0NOV8wz4z++KbEp071f+EAysvAkZ4t2rJCLmK8JeEvdcp6Q
lOooptQmhK04KdxFvy/+OiqmQ7eEygLtaSEms4U0NdskWZIIa8Xs3EAkhVkVV4drwEVdyBbn7UmZ
V0KekGfailpeBhPFq3JNFpisysfkJfnnskEOpJRFBuUEf97kKQ4ktid2Jl5MiIkXaIy7HhjKnvZs
genraLTij6eRQXDxEXaMLbFl3AAsx1RG2YoQOpvs+p3Mw6FR/RqGZdWxNlwfDyFncJ4vXVvzo6s7
CPpcU79T2pHPHceg4oVHhU3ayU4XuBp9cMKICdoWaCdRxR10mmyflh/yRJutU/lYm+oIPP5lz0tx
ueLv82fph/pvGzrw9PDbi9GzSjEVCQYG21jXrfl8R+U3K75fCJ98No80obW9/wGc+f8Bzb4LAxYy
KfDPMH3hRlh+BGD9GUDzCzrsfQCOIwDO13S4P9ZAAw000EADDTTQQAMNNNDAzQIEIMCbByi3CJ7H
iBFusjlv9gOAQYAPbuPGEGJ0bBwm7rgTJm9+nf9WE+Eu7B14UbxnYRp2wz1wLxyG+2q1+szdODMP
B/lM7Q/vveo+vbHhOrU//9vfNMGe+pcUgtiT+j8J4qXbRrS6eaREM850w2jdFsAGn6vbFOdP1G0R
7R/XbSN0E1IZ2bqtPJi5fd/c7kPDuxfG9s9Nz7eXD0/P7tv1/h5BBUZgK2yDMoY0A7fDPphDVx2C
YewXYAz243ga3dSObxxGaxbf2IXzu2EGPoGjaXTg+1vjf/mVHg16Gv4CJdgLBvS4AzpgAsPzIOYD
xTE6myzhE5OIFh9dv8MewYWfv9P+MewD2EDFjLrPxJf5iSlHD9WjL7w8c35mPrXTXnrD5Ddpb39N
WfkBv5+7fCr9tqH6qOlNUw6HPB+0lf8+AGbeycYKZW5kc3RyZWFtDWVuZG9iag0yOSAwIG9iag08
PCANL1R5cGUgL0V4dEdTdGF0ZSANL1NBIGZhbHNlIA0vU00gMC4wMiANL1RSMiAvRGVmYXVsdCAN
Pj4gDWVuZG9iag0xIDAgb2JqDTw8IA0vUyAvRCANPj4gDWVuZG9iag0yIDAgb2JqDTw8IA0vTnVt
cyBbIDAgMSAwIFIgXSANPj4gDWVuZG9iag0zIDAgb2JqDTw8IA0vVHlwZSAvUGFnZXMgDS9LaWRz
IFsgOCAwIFIgXSANL0NvdW50IDEgDT4+IA1lbmRvYmoNNCAwIG9iag08PCANL0NyZWF0aW9uRGF0
ZSAoRDoyMDAzMDIxMjE1Mzc1MSswMicwMCcpDS9Nb2REYXRlIChEOjIwMDMwMjEyMTUzNzUxKzAy
JzAwJykNL1Byb2R1Y2VyIChBY3JvYmF0IERpc3RpbGxlciA1LjAuNSBcKFdpbmRvd3NcKSkNL0F1
dGhvciAoc2F0cmFuKQ0vQ3JlYXRvciAoUFNjcmlwdDUuZGxsIFZlcnNpb24gNS4yKQ0vVGl0bGUg
KE1pY3Jvc29mdCBXb3JkIC0gMDIwMDAyOTI5U09VUkNFIElTQk4gMC02NzktNDU1NzAtMUNELmh0
bSkNPj4gDWVuZG9iag01IDAgb2JqDTw8IC9UeXBlIC9NZXRhZGF0YSAvU3VidHlwZSAvWE1MIC9M
ZW5ndGggMTIwNyA+PiANc3RyZWFtDQo8P3hwYWNrZXQgYmVnaW49JycgaWQ9J1c1TTBNcENlaGlI
enJlU3pOVGN6a2M5ZCcgYnl0ZXM9JzEyMDYnPz48cmRmOlJERiB4bWxuczpyZGY9J2h0dHA6Ly93
d3cudzMub3JnLzE5OTkvMDIvMjItcmRmLXN5bnRheC1ucyMnIHhtbG5zOmlYPSdodHRwOi8vbnMu
YWRvYmUuY29tL2lYLzEuMC8nPjxyZGY6RGVzY3JpcHRpb24gYWJvdXQ9JycgeG1sbnM9J2h0dHA6
Ly9ucy5hZG9iZS5jb20vcGRmLzEuMy8nIHhtbG5zOnBkZj0naHR0cDovL25zLmFkb2JlLmNvbS9w
ZGYvMS4zLycgcGRmOkNyZWF0aW9uRGF0ZT0nMjAwMy0wMi0xMlQxMzozNzo1MVonIHBkZjpNb2RE
YXRlPScyMDAzLTAyLTEyVDEzOjM3OjUxWicgcGRmOlByb2R1Y2VyPSdBY3JvYmF0IERpc3RpbGxl
ciA1LjAuNSAoV2luZG93cyknIHBkZjpBdXRob3I9J3NhdHJhbicgcGRmOkNyZWF0b3I9J1BTY3Jp
cHQ1LmRsbCBWZXJzaW9uIDUuMic+PHBkZjpUaXRsZT5NaWNyb3NvZnQgV29yZCAtIDAyMDAwMjky
OVNPVVJDRSBJU0JOIDAtNjc5LTQ1NTcwLTFDRC5odG08L3BkZjpUaXRsZT48L3JkZjpEZXNjcmlw
dGlvbj4KPHJkZjpEZXNjcmlwdGlvbiBhYm91dD0nJyB4bWxucz0naHR0cDovL25zLmFkb2JlLmNv
bS94YXAvMS4wLycgeG1sbnM6eGFwPSdodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvJyB4YXA6
Q3JlYXRlRGF0ZT0nMjAwMy0wMi0xMlQxMzozNzo1MVonIHhhcDpNb2RpZnlEYXRlPScyMDAzLTAy
LTEyVDEzOjM3OjUxWicgeGFwOkF1dGhvcj0nc2F0cmFuJyB4YXA6TWV0YWRhdGFEYXRlPScyMDAz
LTAyLTEyVDEzOjM3OjUxWic+PHhhcDpUaXRsZT48cmRmOkFsdD48cmRmOmxpIHhtbDpsYW5nPSd4
LWRlZmF1bHQnPk1pY3Jvc29mdCBXb3JkIC0gMDIwMDAyOTI5U09VUkNFIElTQk4gMC02NzktNDU1
NzAtMUNELmh0bTwvcmRmOmxpPjwvcmRmOkFsdD48L3hhcDpUaXRsZT48L3JkZjpEZXNjcmlwdGlv
bj4KPHJkZjpEZXNjcmlwdGlvbiBhYm91dD0nJyB4bWxucz0naHR0cDovL3B1cmwub3JnL2RjL2Vs
ZW1lbnRzLzEuMS8nIHhtbG5zOmRjPSdodHRwOi8vcHVybC5vcmcvZGMvZWxlbWVudHMvMS4xLycg
ZGM6Y3JlYXRvcj0nc2F0cmFuJz48ZGM6dGl0bGU+TWljcm9zb2Z0IFdvcmQgLSAwMjAwMDI5MjlT
T1VSQ0UgSVNCTiAwLTY3OS00NTU3MC0xQ0QuaHRtPC9kYzp0aXRsZT48L3JkZjpEZXNjcmlwdGlv
bj4KPC9yZGY6UkRGPjw/eHBhY2tldCBlbmQ9J3InPz4KZW5kc3RyZWFtDWVuZG9iag14cmVmDTAg
NiANMDAwMDAwMDAwMCA2NTUzNSBmDQowMDAwMDc4MTU4IDAwMDAwIG4NCjAwMDAwNzgxODggMDAw
MDAgbg0KMDAwMDA3ODIzMCAwMDAwMCBuDQowMDAwMDc4Mjk0IDAwMDAwIG4NCjAwMDAwNzg1NjAg
MDAwMDAgbg0KdHJhaWxlcg08PA0vU2l6ZSA2DS9JRFs8MThiOGJiMDU3OWVkNjE0ZTgxZTI0NzU1
MzE3OWM0Nzc+PGIyMmI5YWEyMGJlNmRkMjkyYWI5NDE3YTEzNzdkODAwPl0NPj4Nc3RhcnR4cmVm
DTE3Mw0lJUVPRg0=
--=_mixed 004B757DC2256CCB_=--





From owner-ietf@ietf.org  Thu Feb 13 11:32:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17024;
	Thu, 13 Feb 2003 11:32:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jMHm-0001Nc-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 11:32:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jMEq-0001G3-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 11:29:28 -0500
Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16776
	for <ietf@ietf.org>; Thu, 13 Feb 2003 11:22:29 -0500 (EST)
Received: from extremenetworks.com (unknown [10.18.3.100])
	by gnat.inet.org (Postfix) with ESMTP
	id 6BB4867119; Thu, 13 Feb 2003 11:37:36 -0500 (EST)
Date: Thu, 13 Feb 2003 11:26:06 -0500
Subject: Re: Protocol Action: iSCSI to Proposed Standard
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: "Bob Braden" <braden@ISI.EDU>, <sob@harvard.edu>, <mankin@psg.com>,
        <ips@ece.cmu.edu>, <ietf@ietf.org>
To: "Mallikarjun C." <cbm@rose.hp.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <00e901c2d2cd$d713e890$2cb2e40f@rose.hp.com>
Message-Id: <DA313C24-3F6F-11D7-9068-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, Mallikarjun C. 
wrote:

>> All the Internet documentation with which I am familiar, as well as 
>> the
>
> I think we have a case of overlapping vocabulary from two different 
> domains.
>
> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
> a "SCSI transport protocol" (as opposed to a SCSI application layer 
> protocol).
> Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI 
> conventions.
> That is all the critiqued abstract is trying to describe.

In the context of an *Internet* RFC, it seems sensible to use the normal
Internet terminology -- unless one very very clearly indicates that a
term is being used in some different semantic.  One might postulate that
the document's editors and RFC-Editor could work out a mutually 
agreeable
editorial change here to add clarity.

Ran




From owner-ietf@ietf.org  Thu Feb 13 16:18:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01646;
	Thu, 13 Feb 2003 16:18:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jQhe-0001wD-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 16:15:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jQge-0001sY-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 16:14:28 -0500
Received: from franklin.boulder.nist.gov (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00215
	for <ietf@ietf.org>; Thu, 13 Feb 2003 16:07:23 -0500 (EST)
Received: from JESSESDAD.boulder.nist.gov (jessesdad.timefreq.bldrdoc.gov [132.163.136.30])
	by franklin.boulder.nist.gov (Switch-2.2.4/Switch-2.2.4) with ESMTP id h1DLB8L03869
	for <ietf@ietf.org>; Thu, 13 Feb 2003 14:11:08 -0700 (MST)
Message-Id: <5.1.0.14.2.20030213140534.02e04780@mail.boulder.nist.gov>
X-Sender: mweiss@mail.boulder.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 13 Feb 2003 14:11:07 -0700
To: ietf@ietf.org
From: Marc Weiss <mweiss@boulder.nist.gov>
Subject: NIST/T1X1 Sync Workshop for 2003
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_74555775==_.ALT"
Sender: owner-ietf@ietf.org
Precedence: bulk

--=====================_74555775==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Greetings.
We would like to announce the:


2003 NIST-T1X1 WORKSHOP ON SYNCHRONIZATION IN TELECOMMUNICATION SYSTEMS
Noon March 18 - Noon March 20, 2003


The brochure is available from the t1 web site:
http://www.t1.org/
You may also go to the NIST the web site for more information, including 
on-line registration:
http://www.boulder.nist.gov/timefreq/seminars/t1x1.html

This is the 11th year for this Workshop, the 5th annual in collaboration 
between NIST and T1X1.  This NIST Time and Frequency Division is again 
working with T1X1 personnel and industry experts to put the Workshop 
together this year.  It is a balance between training and exploring new 
questions in Telecom Sync issues.

The Workshop will be focused and more concise this year, as it was last 
year, than previous Workshops.  We hope to make travel more convenient by 
going from noon on Tuesday to noon on Thursday, the equivalent of  2 days 
of lectures.

We will hold the meetings for the workshop at our NIST facilities, though 
the evening reception will be at the Omni Interlocken Resort in Broomfield, 
Colorado, about 10 miles SE of NIST in Boulder.


For questions about registration, please contact:
Wendy Ortega <ortegaw@boulder.nist.gov>

For technical questions about the workshop, please contact:
Marc Weiss <mweiss@boulder.nist.gov>


Thank you,
Marc Weiss

____________________________________________________________________
Marc A. Weiss, Ph.D.                                    Phone:  303/497-3261
NIST Time and Frequency Division                FAX:    303/497-6461
MS 847.5, 325 Broadway
Boulder, CO  80305-3328
____________________________________________________________________ 
--=====================_74555775==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Greetings.<br>
We would like to announce the:<br><br>
<br>
<div align="center"><font size=4><b>2003 NIST-T1X1 WORKSHOP ON
SYNCHRONIZATION IN TELECOMMUNICATION SYSTEMS<br>
Noon March 18 - Noon March 20, 2003<br><br>
<br>
</b></font></div>
The brochure is available from the t1 web site:<br>
<a href="http://www.t1.org/" eudora="autourl">http://www.t1.org/</a><br>
You may also go to the NIST the web site for more information, including
on-line registration:<br>
<a href="http://www.boulder.nist.gov/timefreq/seminars/t1x1.html" eudora="autourl">http://www.boulder.nist.gov/timefreq/seminars/t1x1.html</a><br><br>
This is the 11th year for this Workshop, the 5th annual in collaboration
between NIST and T1X1.&nbsp; This NIST Time and Frequency Division is
again working with T1X1 personnel and industry experts to put the
Workshop together this year.&nbsp; It is a balance between training and
exploring new questions in Telecom Sync issues.<br><br>
The Workshop will be focused and more concise this year, as it was last
year, than previous Workshops.&nbsp; We hope to make travel more
convenient by going from noon on Tuesday to noon on Thursday, the
equivalent of&nbsp; 2 days of lectures.&nbsp; <br><br>
We will hold the meetings for the workshop at our NIST facilities, though
the evening reception will be at the Omni Interlocken Resort in
Broomfield, Colorado, about 10 miles SE of NIST in Boulder.&nbsp;
<br><br>
<br>
For questions about registration, please contact:<br>
Wendy Ortega &lt;ortegaw@boulder.nist.gov&gt;<br><br>
For technical questions about the workshop, please contact:<br>
Marc Weiss &lt;mweiss@boulder.nist.gov&gt;<br><br>
<br>
Thank you,<br>
Marc Weiss<br><br>
____________________________________________________________________<br>
Marc A. Weiss,
Ph.D.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Phone:&nbsp;
303/497-3261<br>
NIST Time and Frequency Division&nbsp;&nbsp;&nbsp;&nbsp;
<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>FAX:&nbsp;&nbsp;&nbsp;
303/497-6461<br>
MS 847.5, 325 Broadway<br>
Boulder, CO&nbsp; 80305-3328<br>
____________________________________________________________________
</html>

--=====================_74555775==_.ALT--




From owner-ietf@ietf.org  Thu Feb 13 21:45:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27264;
	Thu, 13 Feb 2003 21:45:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jVq3-0005rU-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 21:44:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jVo9-0005eB-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 21:42:33 -0500
Received: from rip.psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27092
	for <ietf@ietf.org>; Thu, 13 Feb 2003 21:35:26 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=rip.psg.com)
	by rip.psg.com with esmtp (Exim 4.12)
	id 18jVkt-0008PS-00
	for ietf@ietf.org; Thu, 13 Feb 2003 18:39:11 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Feb 2003 18:39:11 -0800
To: ietf <ietf@ietf.org>
Subject: movies vs chat logs
Message-Id: <E18jVkt-0008PS-00@rip.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

due to lightening struck tower, i was unable to be at the atlanta
meeting.  i really needed to know what happened in a number of
sessions in which i have critical interest.

the jabber logs were useless, at best "s/he is talking about X now"
with no idea of what was said, how it was justified, what the
reactions were, ...  note that i am a jabber user, run a jabber
server, ...  so it is not anti-jabber prejudice.  it just seemed
not to work in this particular context for this particular use.
perhaps it kept folk with insufficient email amused during boring
times :-).

by happenstance, most of the sessions i cared about most were
recorded by the mbone team.  i downloaded the mpgs, and have
found them *very* useful.  it is like being there, but without
the opportunity to put my foot in my mouth.  i am not sure how
useful the stuff was in real-time broadcast.  but the recordings
sure are a real help.

randy




From owner-ietf@ietf.org  Thu Feb 13 22:06:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27740;
	Thu, 13 Feb 2003 22:06:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jWDH-0007AJ-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 22:08:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jWCJ-000778-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 22:07:31 -0500
Received: from garlic.apnic.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27591
	for <ietf@ietf.org>; Thu, 13 Feb 2003 22:00:23 -0500 (EST)
Received: (from ggm@localhost)
	by garlic.apnic.net (8.11.6/8.11.6) id h1E336N00986;
	Fri, 14 Feb 2003 13:03:06 +1000 (EST)
Date: Fri, 14 Feb 2003 13:03:06 +1000
From: George Michaelson <ggm@apnic.net>
Cc: ietf@ietf.org
Subject: Re: movies vs chat logs
Message-Id: <20030214130306.680538db.ggm@apnic.net>
In-Reply-To: <E18jVkt-0008PS-00@rip.psg.com>
References: <E18jVkt-0008PS-00@rip.psg.com>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I found the jabber logs helped me decide when to move between sessions, when
micro-timing of schedules wasn't apparent and I had to be in 'both' sessions.

I found sidebar conversations carried the subjective information you missed. I
don't think we can yet intuit the consensus of the room to put that into
jabber in the wide, one mans bozo is another mans guru and all that...

I think you are right to characterize the recordings as 'being there with
sanity checks' -The jabber stuff was a way I found I could meet two goals:

	1) let other people know whats going on in the room

	2) compile the data which the WG chair wanted as a log of the session
	   tending towards the official minutes

On the whole, I liked having the jabber even if the value is moot. Writing a
jabber log is very painful. RSI returns!

cheers

-george



From owner-ietf@ietf.org  Thu Feb 13 22:33:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28456;
	Thu, 13 Feb 2003 22:33:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jWcQ-0008LE-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 22:34:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jWbd-0008JA-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 22:33:41 -0500
Received: from cobalt.sopac.org.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28074
	for <ietf@ietf.org>; Thu, 13 Feb 2003 22:26:00 -0500 (EST)
Received: by cobalt.sopac.org.fj (Postfix, from userid 416)
	id C466D17C3F; Fri, 14 Feb 2003 03:25:59 +0000 (UTC)
Received: from bigiron.sopac.org.fj (unknown [10.0.0.180])
	by cobalt.sopac.org.fj (Postfix) with ESMTP id 7EC7317C09
	for <ietf@ietf.org>; Fri, 14 Feb 2003 03:25:59 +0000 (UTC)
Received: by BIGIRON with Internet Mail Service (5.5.2650.21)
	id <CYRCVPF5>; Fri, 14 Feb 2003 15:29:00 +1200
Message-ID: <F12ECEA0435AD211B5280008C7ACBC85016B4909@BIGIRON>
From: Franck Martin <Franck@sopac.org>
To: ietf@ietf.org
Subject: RE: movies vs chat logs
Date: Fri, 14 Feb 2003 15:28:58 +1200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
Sender: owner-ietf@ietf.org
Precedence: bulk

I'm very curious about your experience with jabber conference. This seems
very interesting.. Is the conference still running on so I can check for
myself? pointers?

Also I'm curious about the technology used to stream video over the mbone.
Can you give me some pointers?

Franck Martin

> -----Original Message-----
> From: George Michaelson [mailto:ggm@apnic.net]
> Sent: Friday, 14 February 2003 3:03 
> Cc: ietf@ietf.org
> Subject: Re: movies vs chat logs
> 
> 
> 
> I found the jabber logs helped me decide when to move between 
> sessions, when
> micro-timing of schedules wasn't apparent and I had to be in 
> 'both' sessions.
> 
> 



From owner-ietf@ietf.org  Thu Feb 13 23:34:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29826;
	Thu, 13 Feb 2003 23:34:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jXXY-0003F1-00
	for ietf-list@ran.ietf.org; Thu, 13 Feb 2003 23:33:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jXWP-0003B4-00
	for ietf@ran.ietf.org; Thu, 13 Feb 2003 23:32:21 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29543
	for <ietf@ietf.org>; Thu, 13 Feb 2003 23:25:13 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 3792A4CE4F; Thu, 13 Feb 2003 23:28:59 -0500 (EST)
Received: from berkshire.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id XAA13422;
	Thu, 13 Feb 2003 23:28:58 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 89B697B4D; Thu, 13 Feb 2003 23:28:57 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: Randy Bush <randy@psg.com>
Cc: ietf <ietf@ietf.org>
Subject: Re: movies vs chat logs 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Feb 2003 23:28:57 -0500
Message-Id: <20030214042857.89B697B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

In message <E18jVkt-0008PS-00@rip.psg.com>, Randy Bush writes:
>due to lightening struck tower, i was unable to be at the atlanta
>meeting.  i really needed to know what happened in a number of
>sessions in which i have critical interest.
>
>the jabber logs were useless, at best "s/he is talking about X now"
>with no idea of what was said, how it was justified, what the
>reactions were, ...  note that i am a jabber user, run a jabber
>server, ...  so it is not anti-jabber prejudice.  it just seemed
>not to work in this particular context for this particular use.
>perhaps it kept folk with insufficient email amused during boring
>times :-).
>

It depends on the session and the volunteer scribe.  I did it for a 
while, found it very hard, but very much appreciated the much-better 
efforts of others in some wgs.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Fri Feb 14 00:53:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01106;
	Fri, 14 Feb 2003 00:53:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jYlz-0008U3-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 00:52:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jYlf-0008Rm-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 00:52:12 -0500
Received: from shego.dbc.mtview.ca.us (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00970
	for <ietf@ietf.org>; Fri, 14 Feb 2003 00:45:04 -0500 (EST)
Received: from shego.dbc.mtview.ca.us (localhost [127.0.0.1])
	by shego.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h1E5mk8u003894;
	Thu, 13 Feb 2003 21:48:46 -0800 (PST)
Date: Thu, 13 Feb 2003 21:48:45 -0800
From: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
To: Randy Bush <randy@psg.com>
Cc: ietf@ietf.org
Subject: Re: movies vs chat logs
Message-Id: <20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us>
In-Reply-To: <E18jVkt-0008PS-00@rip.psg.com>
References: <E18jVkt-0008PS-00@rip.psg.com>
Organization: Dover Beach Consulting, Inc.
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> the jabber logs were useless, at best "s/he is talking about X now"
> with no idea of what was said, how it was justified, what the
> reactions were, ...  note that i am a jabber user, run a jabber
> server, ...  so it is not anti-jabber prejudice.  it just seemed
> not to work in this particular context for this particular use.
> perhaps it kept folk with insufficient email amused during boring
> times :-).

as someone who was in atlanta, the jabber conferencing allowed me to be in two
places at once, and gauge which room(s) i needed to be in...

were some logs more useful to you than others?  if so, what features of that
logging was helpful. since we've got another meeting coming up in a month, now
would be a good time for us to start giving advice to folks...

/mtr
 



From owner-ietf@ietf.org  Fri Feb 14 01:36:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01820;
	Fri, 14 Feb 2003 01:36:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jZTW-0006Vx-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 01:37:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jZTP-0006Tk-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 01:37:23 -0500
Received: from rip.psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01635
	for <ietf@ietf.org>; Fri, 14 Feb 2003 01:30:15 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=rip.psg.com)
	by rip.psg.com with esmtp (Exim 4.12)
	id 18jZQ7-00096J-00; Thu, 13 Feb 2003 22:33:59 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Feb 2003 22:33:58 -0800
To: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
Cc: ietf@ietf.org
Subject: Re: movies vs chat logs
References: <E18jVkt-0008PS-00@rip.psg.com>
	<20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us>
Message-Id: <E18jZQ7-00096J-00@rip.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> were some logs more useful to you than others?

yes.  but the difference between 5% useful and twice as good is not
very interesting.

i have used jabber in ietf meetings and similarcontexts.  it works
to coordinate stuff in real-time.  but that was not my application
this time.  i really was after the as much content of the meeting
as possible.  to do that well in jabber or whatever, one would have
to pay a court transcription person.  whereas, as someone already
pointed out, a cheap video camera does the job.

randy




From owner-ietf@ietf.org  Fri Feb 14 02:55:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12745;
	Fri, 14 Feb 2003 02:55:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jag2-00017W-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 02:54:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jacV-0000zc-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 02:50:51 -0500
Received: from mailf.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12616
	for <ietf@ietf.org>; Fri, 14 Feb 2003 02:43:39 -0500 (EST)
Received: from d1o888.telia.com (d1o888.telia.com [213.67.172.241])
	by mailf.telia.com (8.12.5/8.12.5) with ESMTP id h1E7lLjd006405;
	Fri, 14 Feb 2003 08:47:21 +0100 (CET)
X-Original-Recipient: ietf@ietf.org
Received: from pi.se (h70n2fls31o888.telia.com [213.64.120.70])
	by d1o888.telia.com (8.10.2/8.10.1) with ESMTP id h1E7lH215036;
	Fri, 14 Feb 2003 08:47:20 +0100 (CET)
Message-ID: <3E4C9E1E.1010406@pi.se>
Date: Fri, 14 Feb 2003 08:43:26 +0100
From: Loa Andersson <loa@pi.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RJ Atkinson <rja@extremenetworks.com>
CC: "Mallikarjun C." <cbm@rose.hp.com>, Bob Braden <braden@ISI.EDU>,
        sob@harvard.edu, mankin@psg.com, ips@ece.cmu.edu, ietf@ietf.org
Subject: Re: Protocol Action: iSCSI to Proposed Standard
References: <DA313C24-3F6F-11D7-9068-00039357A82A@extremenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Ran,

would agree to this, and put even stronger

"... Internet RFCs the normal Inernet terminology SHOULD be used, unless 
there
are very stong and explicitly stated reasons not to ..."

it should als  be that the I* have a guiding role in this

/Loa


RJ Atkinson wrote:

>
> On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, Mallikarjun C. 
> wrote:
>
>>> All the Internet documentation with which I am familiar, as well as the
>>
>>
>> I think we have a case of overlapping vocabulary from two different 
>> domains.
>>
>> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
>> a "SCSI transport protocol" (as opposed to a SCSI application layer 
>> protocol).
>> Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI 
>> conventions.
>> That is all the critiqued abstract is trying to describe.
>
>
> In the context of an *Internet* RFC, it seems sensible to use the normal
> Internet terminology -- unless one very very clearly indicates that a
> term is being used in some different semantic.  One might postulate that
> the document's editors and RFC-Editor could work out a mutually agreeable
> editorial change here to add clarity.
>
> Ran
>
>
>
>





From owner-ietf@ietf.org  Fri Feb 14 05:37:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15678;
	Fri, 14 Feb 2003 05:37:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jdCo-0006ug-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 05:36:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jdBq-0006sp-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 05:35:30 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA15569
	for <ietf@ietf.org>; Fri, 14 Feb 2003 05:28:18 -0500 (EST)
Received: (qmail 71053 invoked by uid 1016); 14 Feb 2003 10:32:28 -0000
Date: 14 Feb 2003 10:32:28 -0000
Message-ID: <20030214103228.71052.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: axfr-clarify's fraudulent claims of consensus
References: <200302101659.LAA15654@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

This ``clarification'' document prohibits several perfectly legitimate,
very widely deployed, AXFR implementation techniques. See my web page
http://cr.yp.to/djbdns/axfr-clarify.html for details. In particular,
this document violates RFC 2119, section 6, in five separate ways.

At least seven people have gone on record as objecting to axfr-clarify:

   Dean Anderson,
   Len Budney,
   Felix von Leitner,
   Kenji Rikitake,
   Aaron Swartz,
   Sam Trenholme (MaraDNS implementor), and
   me (djbdns implementor).

Furthermore, the Yokohama minutes report a WG decision that axfr-clarify
is ``too bind specific''---too specific to BIND 9, to be precise.

Despite this decision and these extensive objections, the WG chairs
declared ``consensus'' for axfr-clarify and sent it to the IESG. Those
claims of consensus were clearly fraudulent: there was no WG discussion
of axfr-clarify in the interim! Subsequent discussions did not resolve
any of the objections.

A review of all of the axfr-clarify discussions in the WG list archive
shows that this document is being pushed primarily by people who have
been paid for BIND work: Mark Andrews, Roy Arends, David Conrad, Danny
Mayer, Jim Reid, Paul Vixie, Brian Wellington, document author Andreas
Gustafsson, and WG chair Gudmundsson.

There are non-BIND people who support the document, notably PowerDNS
implementor Bert Hubert, but my understanding is that Hubert's support
is based entirely on the hope that this document will prevent future
interoperability problems, without regard to the huge redeployment costs
that this document is imposing on the users of existing implementations.

Note that the users attacked by this document include BIND 8 users---who
are no longer represented in the WG by implementors, now that the BIND
implementors are pushing BIND 9. The document's proponents admit that
their ``clarification'' imposes rules disobeyed by BIND 8. My survey
http://cr.yp.to/surveys/dns1.html two months ago showed that 45% of all
.com names were served by BIND 8, while only 23% were served by BIND 9.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago

P.S. You know what really amazes me about this? In another forum, a few
people, including a former IESG member, are objecting to an incredibly
valuable requirement that software support a universal encoding (UTF-8)
of a universal character set (Unicode). Why? Because this requirement
would force some existing software to change---and these people claim
that the IETF _never_ demands changes from deployed software that
complies with the previous standards.



From owner-ietf@ietf.org  Fri Feb 14 06:47:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17240;
	Fri, 14 Feb 2003 06:47:28 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jeEg-00010e-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 06:42:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jeES-0000yg-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 06:42:16 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16377;
	Fri, 14 Feb 2003 06:35:03 -0500 (EST)
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1EBcVq27692;
	Fri, 14 Feb 2003 18:38:31 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1EBcMb10699;
	Fri, 14 Feb 2003 18:38:24 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <20030214103228.71052.qmail@cr.yp.to> 
References: <20030214103228.71052.qmail@cr.yp.to>  <200302101659.LAA15654@ietf.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 14 Feb 2003 18:38:22 +0700
Message-ID: <10697.1045222702@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        14 Feb 2003 10:32:28 -0000
    From:        "D. J. Bernstein" <djb@cr.yp.to>
    Message-ID:  <20030214103228.71052.qmail@cr.yp.to>

  | This ``clarification'' document prohibits several perfectly legitimate,
  | very widely deployed, AXFR implementation techniques.

It prohibits some odd-ball techniques that risk future enhancements
(and generally clarifies the almost non-existant specification).

  | In particular,
  | this document violates RFC 2119, section 6, in five separate ways.

2119 is a list of words with definitions to save other RFCs from having
to define them over and over again.   It has some recommendations about
where the words should be used - but it is always up to the document in
question (the WG for a WG document) to decide which of those words should
be used in what circumstances (or to ignore 2119 completely if so inclined).
"Violating" 2119 is a nonsense concept.

  | Furthermore, the Yokohama minutes report a WG decision that axfr-clarify
  | is ``too bind specific''---too specific to BIND 9, to be precise.

That related to some of the language in the draft I believe (I was there,
and I think was one of those who supported this position).   Some of that
I still believe could be cleaned up to be nicer.   It doesn't relate to
any of the substance though, nor particularly to BIND 9, but rather to use
of terms like "slave" and "master" which are (recent) BIND inventions to
refer to what the DNS (1034/1035) has always used the words "secondary"
and "primary" for.   There's a bit more like that I think as well.  None
of it really matters, though the doc would be better if it was all fixed.

  | Despite this decision and these extensive objections, the WG chairs
  | declared ``consensus'' for axfr-clarify and sent it to the IESG.

I believe rough consensus exists on this one (it is rough, but there's
certainly much more support than opposition).

  | A review of all of the axfr-clarify discussions in the WG list archive
  | shows that this document is being pushed primarily by people who have
  | been paid for BIND work:

Even if this were true (and I don't believe it is - I have never been
paid for any BIND work) it is irrelevant.   It is not at all unusual
for a group of related people (sometimes all actually currently employed
by one organisation) to push a proposal.

  | Note that the users attacked by this document include BIND 8 users---who
  | are no longer represented in the WG by implementors, now that the BIND
  | implementors are pushing BIND 9. The document's proponents admit that
  | their ``clarification'' imposes rules disobeyed by BIND 8. My survey
  | http://cr.yp.to/surveys/dns1.html two months ago showed that 45% of all
  | .com names were served by BIND 8, while only 23% were served by BIND 9.

What has this to do with anything?   All that is being done here is to
tighten up the specification for how AXFR is supposed to be done.   That
old BIND code has bugs can hardly be news (even older BIND code had
millions of bugs).   Nothing proposed is going to cause failures of
any existing implementations, nor any current implementations to fail to
interoperate with any new implementations that follow this clarification.

The scare mongering about "huge redeployment costs" is utter nonsense,
no-one is being asked to redeploy anything.

All this document seeks to do is to get future AXFR implementations to
be a little tighter in what they do, so that some possible (even worse)
implementations bugs would have less bad effects than they might otherwise
have done.

The effect upon your implementation would be, that unless you alter
your implementation, you wouldn't be able to claim that it is conformant
with this new RFC (once it is issued of course).   That's it.   As you
seem to dislike AXFR as a zone transfer mechanism anyway (which is just
fine, it has never been required) I'm not sure why you'd care.

kre





From owner-ietf@ietf.org  Fri Feb 14 09:49:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23792;
	Fri, 14 Feb 2003 09:49:06 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jh05-0000Hr-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 09:39:37 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jgJI-0006P4-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 08:55:24 -0500
Received: from outpost.ds9a.nl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22655;
	Fri, 14 Feb 2003 08:48:10 -0500 (EST)
Received: by outpost.ds9a.nl (Postfix, from userid 1000)
	id B3BA44615; Fri, 14 Feb 2003 14:51:55 +0100 (CET)
Date: Fri, 14 Feb 2003 14:51:55 +0100
From: bert hubert <ahu@ds9a.nl>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
Message-ID: <20030214135155.GA8342@outpost.ds9a.nl>
References: <200302101659.LAA15654@ietf.org> <20030214103228.71052.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030214103228.71052.qmail@cr.yp.to>
User-Agent: Mutt/1.3.28i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, Feb 14, 2003 at 10:32:28AM -0000, D. J. Bernstein wrote:

> This ``clarification'' document prohibits several perfectly legitimate,
> very widely deployed, AXFR implementation techniques. See my web page
> http://cr.yp.to/djbdns/axfr-clarify.html for details. In particular,
> this document violates RFC 2119, section 6, in five separate ways.

See me not care. Almost all RFCs are mutually contradictory. This is not
math, and even there we have Goedel. Some observations. 

Does this clarify things
------------------------

Well, yes. It also specifies new behaviour. The name is therefore
wrong. I'd move to just call this RFC the 'New AXFR RFC' and be done with
it. It should then also specify that nameservers should have configuration
options to deal with older servers.

Otherwise, I'd be more than happy with a non-semantics changing version of
this draft, one that just documents how to start an AXFR and how to finish
it.

The Zone
--------
Your software does not know about zones, it appears. Much of your criticism
boils down to the fact that you do not have a zone concept and do not want
to have one, where 1034 and 1035 simply ooze with zone definitions and they
are clearly part of the DNS philosophy.

Could you perhaps separate your criticism into the parts that are truly
stupid and the parts that just don't fit in with your architecture? 

At a very early point, PowerDNS also did not have zones but it turns out to
be hard to do proper interoperation without them.

  "Therefore, in a zone transfer the master MUST send exactly those
   records that are associated with the zone, whether or not their owner
   names would be considered to be "in" the zone for purposes of
   resolution, and whether or not they would be eligible for use as glue
   in responses"

I don't really get this one on second or third reading. Does this condone
weird data in a zone, data that does not end on the zone name? Like the
examples you mention?

>    Dean Anderson, Len Budney, Felix von Leitner, Kenji Rikitake, Aaron
>    Swartz, Sam Trenholme (MaraDNS implementor), and me (djbdns
>    implementor).

I object to the naming, this goes beyond clarification. Calling BIND9
behaviour 'existing practice' is bad politics. I hate this part:

"and slaves MUST ignore any duplicate RRs received.". I know this is about
robustness but it makes an incoming AXFR a O(N^2) operation which sucks.
Yes, you could build sophisticated hashes & stuff but why not put the burden
on the server supplying the zone. It has had to load the zone at least once
anyhow.

> is based entirely on the hope that this document will prevent future
> interoperability problems, without regard to the huge redeployment costs
> that this document is imposing on the users of existing implementations.

Stuff changes anyhow. Otherwise we'd still be running NCP and HOSTS.TXT. I
do like to have the ability to add TSIGs to an AXFR in the additional
section, even if that potentially breaks older remotes.

Regards,

bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl                         Consulting





From owner-ietf@ietf.org  Fri Feb 14 09:59:23 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23999;
	Fri, 14 Feb 2003 09:59:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jhH2-0001f9-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 09:57:08 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jhBH-00014x-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 09:51:11 -0500
Received: from thunker.thunk.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23704
	for <ietf@ietf.org>; Fri, 14 Feb 2003 09:43:57 -0500 (EST)
Received: from [216.175.175.162] (helo=think.thunk.org)
	by thunker.thunk.org with asmtp (Exim 3.35 #1 (Debian))
	id 18jh7R-0005d3-00; Fri, 14 Feb 2003 09:47:13 -0500
Received: from tytso by think.thunk.org with local (Exim 3.36 #1 (Debian))
	id 18jh7Q-0000Sk-00; Fri, 14 Feb 2003 09:47:12 -0500
Date: Fri, 14 Feb 2003 09:47:12 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: Randy Bush <randy@psg.com>
Cc: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>, ietf@ietf.org
Subject: Re: movies vs chat logs
Message-ID: <20030214144712.GB26345@think.thunk.org>
References: <E18jVkt-0008PS-00@rip.psg.com> <20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us> <E18jZQ7-00096J-00@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E18jZQ7-00096J-00@rip.psg.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Feb 13, 2003 at 10:33:58PM -0800, Randy Bush wrote:
> 
> i have used jabber in ietf meetings and similarcontexts.  it works
> to coordinate stuff in real-time.  but that was not my application
> this time.  i really was after the as much content of the meeting
> as possible.  to do that well in jabber or whatever, one would have
> to pay a court transcription person.  whereas, as someone already
> pointed out, a cheap video camera does the job.

On the other hand, it's much faster and convenient to scan (and
search) a text transcript compared to viewing a video feed.  It also
takes up less space to store.  It's extremely amusing to think of a
scribe as a compression algorithm, but that's basically what's going
on.  Unfortunately, as always, compression can sometimes be expensive.

In some cases we might be able to get cheap grad students.  Or perhaps
we could find people who would be willing to transcribe 2 or 3 wg
sessions that they aren't otherwise participating in exchange for a
deep discount on their registration fee?  There would need to be some
quality control (maybe the wg chair has to certify afterwards that the
transcript was an accurate record of the proceedings), but it would
help make much better minutes.

Of course, there are some downsides to having a non-participant scribe
or take minutes for a meeting.  Someone who is familiar with the
background, context, and (unfortunately, sometimes) jargon of a
working group can often take better minutes than an outsider.  On the
other hand, it is very hard to take good minutes and/or scribe while
participating in the discussion, and often the minutes will suffer for
those portions of the meeting where the minute-taker also wants to
join into the discussion.  (Or stand in line at the mike, etc.)

That being said, though, I think that if the scribe was comprehensive
enough, and the text was then immediately reviewed by the wg chairs
and other core participants in the meeting, while the discusions was
still fresh in their minds, the result might be a much *better* record
of what happened than the current system of taking minutes for the
meeting.

						- Ted




From owner-ietf@ietf.org  Fri Feb 14 09:59:25 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24022;
	Fri, 14 Feb 2003 09:59:25 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jhJM-0001vO-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 09:59:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jhIN-0001qm-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 09:58:31 -0500
Received: from rip.psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23866
	for <ietf@ietf.org>; Fri, 14 Feb 2003 09:51:17 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=rip.psg.com)
	by rip.psg.com with esmtp (Exim 4.12)
	id 18jhEz-000Aih-00; Fri, 14 Feb 2003 06:55:01 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Feb 2003 06:55:01 -0800
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ietf@ietf.org
Subject: Re: movies vs chat logs
References: <E18jVkt-0008PS-00@rip.psg.com>
	<20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us>
	<E18jZQ7-00096J-00@rip.psg.com>
	<20030214144712.GB26345@think.thunk.org>
Message-Id: <E18jhEz-000Aih-00@rip.psg.com>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> On the other hand, it's much faster and convenient to scan (and
> search) a text transcript compared to viewing a video feed.  It
> also takes up less space to store.  It's extremely amusing to
> think of a scribe as a compression algorithm, but that's
> basically what's going on.  Unfortunately, as always, compression
> can sometimes be expensive.

in my application, it was the lossiness which bothered me.  and,
while making searching easy is wonderful, it is useless if the
content itself is not there.

once again, my use mode, which in no way claim is the only one of
interest, was to get as much of the content of the sessions as
possible.  the jabber logs contain 1-5% of the technical and social
content of the videos.

randy




From owner-ietf@ietf.org  Fri Feb 14 12:38:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28322;
	Fri, 14 Feb 2003 12:38:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jiF7-0005Xw-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 10:59:13 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jiA2-0005Es-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 10:53:58 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25290
	for <ietf@ietf.org>; Fri, 14 Feb 2003 10:46:43 -0500 (EST)
Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h1EFoJB6022008
	for <ietf@ietf.org>; Fri, 14 Feb 2003 07:50:19 -0800 (PST)
Received: from cisco.com (sjc-vpn4-764.cisco.com [10.21.82.252])
	by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA)
	with SMTP id AEE34835;
	Fri, 14 Feb 2003 07:36:18 -0800 (PST)
Received: by cisco.com (sSMTP sendmail emulation); Fri, 14 Feb 2003 10:50:27 -0500
Date: Fri, 14 Feb 2003 10:50:27 -0500
From: Scott W Brim <sbrim@cisco.com>
To: ietf@ietf.org
Subject: Re: movies vs chat logs
Message-ID: <20030214155026.GF2300@sbrim-w2k>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>, ietf@ietf.org
References: <E18jVkt-0008PS-00@rip.psg.com> <20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030213214845.10281764.mrose+mtr.netnews@dbc.mtview.ca.us>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

It has potential, but not much more potential than if someone emailed a
transcript at the end of the meeting.

If you are interested in the meeting, but can't be there because you are
not on-site, video is still far better.  No transcript can possibly show
the chair's facial expression as a question is asked and answered.
Nuances are important in understanding how and why decisions are made.

If you are interested but can't be there because of a conflict, then you
*could* watch the chat in real time but then you are not participating
fully in either meeting.  The main benefit here imho is to know when a
particular subject is going to be discussed.  For that you might just
get someone to send a msg to your mobile.

Transcripts are better because they can be edited for clarity during low
points in the discussion.

Personally I admired the effort that went into making the chat work, but
got nothing out of it except to know when particular topics were being
discussed -- after the discussion had already started.

On the other hand, I'm all in favor of tools for realtime discussion in
between physical meetings.  I think it would be great to have per-WG
IETF virtual hangouts with shared whiteboards and more.  

..Scott



From owner-ietf@ietf.org  Fri Feb 14 12:55:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28847;
	Fri, 14 Feb 2003 12:55:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jk06-0003qj-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 12:51:50 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jjd9-0002pm-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 12:28:07 -0500
Received: from bean.ar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27772
	for <ietf@ietf.org>; Fri, 14 Feb 2003 12:20:50 -0500 (EST)
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h1EHOamn019283
	for <ietf@ietf.org>; Fri, 14 Feb 2003 09:24:36 -0800 (PST)
Date: Fri, 14 Feb 2003 09:24:35 -0800 (PST)
From: Rick Wesson <wessorh@ar.com>
To: <ietf@ietf.org>
Subject: Re: Internet-Draft Cutoff Dates for San Francisco, CA (March 16-21,
 2003) 
In-Reply-To: <200302141458.JAA23987@ietf.org>
Message-ID: <Pine.LNX.4.33.0302140922440.664-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


Could we see these cutoff dates on the main meeting page, since they
change and the location of this document isn't well know.


thanks,

-rick



On Fri, 14 Feb 2003, Internet-Drafts Administrator wrote:

>
> NOTE: There are two (2) Internet-Draft Cutoff dates
>
> February 24th: Cutoff for Initial Submissions (new documents)
>
> All initial submissions(-00) must be submitted by Monday, February 24th,
> at 09:00 ET.  Initial submissions received after this time will NOT be
> made available in the Internet-Drafts directory, and will have to be
> resubmitted.
>
>
> As before, all initial submissions (-00.txt) with a filename beginning
> with a draft-ietf MUST be approved by the appropriate WG Chair prior to
> processing and announcing. WG Chair approval must be received by
> Monday, February 24th.
>
>  Please do NOT wait until the last minute to submit.
>
> Be advised: NO placeholders. Updates to initial submissions received
>             the week of February 24th will NOT be accepted.
>
> March 3rd: FINAL Internet-Draft Cutoff
>
> All revised Internet-Draft submissions must be submitted by Monday,
> March 3rd, 2003 at 09:00 ET.  Internet-Drafts received after this
> time will NOT be announced NOR made available in the Internet-Drafts
> Directories.
>
> We will begin accepting Internet-Draft submissions the week of the
> meeting, though announcements will NOT be sent until the IETF meeting
> is over.
>
> Thank you for your understanding and cooperation. Please do not hesitate
> to contact us if you have any questions or concenrs.
>
> FYI: These and other significant dates can be found at
>       http://www.ietf.org/meetings/cutoff_dates_56.html
>
>




From owner-ietf@ietf.org  Fri Feb 14 12:55:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28869;
	Fri, 14 Feb 2003 12:55:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jk07-0003rX-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 12:51:51 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jjlB-0003AB-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 12:36:25 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28056
	for <ietf@ietf.org>; Fri, 14 Feb 2003 12:29:07 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h1EHWqb11963;
	Fri, 14 Feb 2003 09:32:52 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id RAA04670;
	Fri, 14 Feb 2003 17:32:52 GMT
Date: Fri, 14 Feb 2003 17:32:52 GMT
Message-Id: <200302141732.RAA04670@gra.isi.edu>
To: randy@psg.com, tytso@mit.edu
Subject: Re: movies vs chat logs
Cc: mrose+mtr.netnews@dbc.mtview.ca.us, ietf@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> working group can often take better minutes than an outsider.  On the
  *> other hand, it is very hard to take good minutes and/or scribe while
  *> participating in the discussion, and often the minutes will suffer for
  *> those portions of the meeting where the minute-taker also wants to
  *> join into the discussion.  (Or stand in line at the mike, etc.)

In any of the WG meetings I have attended in the last 10 years, it would
not have been hard to find a person in the room who was not participating
in the discussion.  In fact, 95-99% of the people in the room were
non-participants and were therefore potential note takers.

Bob Braden

  *> 



From owner-ietf@ietf.org  Fri Feb 14 13:54:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00846;
	Fri, 14 Feb 2003 13:54:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jkzi-00071s-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 13:55:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jkzZ-00070G-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 13:55:21 -0500
Received: from bean.ar.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00674
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:48:05 -0500 (EST)
Received: from flash.ar.com (wessorh@flash [66.123.187.80])
	by bean.ar.com (8.12.6/8.12.6) with ESMTP id h1EIpomn028017;
	Fri, 14 Feb 2003 10:51:50 -0800 (PST)
Date: Fri, 14 Feb 2003 10:51:49 -0800 (PST)
From: Rick Wesson <wessorh@ar.com>
To: John C Klensin <john-ietf@jck.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet-Draft Cutoff Dates for San Francisco, CA (March 16-21,
 2003)
In-Reply-To: <410796153.1045230494@p3.JCK.COM>
Message-ID: <Pine.LNX.4.33.0302141049310.664-100000@flash.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



ok, got it. I had looked for the dates last week and couldn't find them.
consider me now, clued.

-rick


On Fri, 14 Feb 2003, John C Klensin wrote:

>
>
> --On Friday, 14 February, 2003 09:24 -0800 Rick Wesson
> <wessorh@ar.com> wrote:
>
> > Could we see these cutoff dates on the main meeting page,
> > since they change and the location of this document isn't well
> > know.
>
> Rick,
>
> The Secretariat is almost certainly better at reading minds than
> I am, but I don't quite understand what you want here.   On what
> I think of as the "main meeting page"
> (http://www.ietf.org/meetings/IETF-56.html for this meeting),
> there is a link called "Important Meeting Dates".  It leads to a
> page that has these dates, and the registration cutoffs, etc.,
> on it.  Do you think we need:
>
> 	(i) To change "Important Meeting Dates" to "Important
> 	Meeting Dates, including I-D cutoffs"?
>
> 	(ii) To move some or all of those dates onto the main
> 	meeting page?  That ought to be possible since neither
> 	the main meeting page or the referenced one are very
> 	long.
>
> 	(iii) To put a note onto the cutoff dates page
> 	(http://www.ietf.org/meetings/cutoff_dates_56.html) that
> 	contains all of the prohibitions, threats, and
> 	explanations about what happens if one misses the
> 	deadline and when documents can next be submitted from
> 	the mailing list announcement?   That information hasn't
> 	changed for years, but it probably should be easier for
> 	the new and/or forgetful to find.
>
> Just trying to clarify... I don't have any strong opinions about
> this.
>
>       john
>
>
>




From owner-ietf@ietf.org  Fri Feb 14 13:54:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00869;
	Fri, 14 Feb 2003 13:54:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jkwy-0006wv-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 13:52:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jkw7-0006v5-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 13:51:47 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00578
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:44:31 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18jksg-000F8V-00; Fri, 14 Feb 2003 13:48:14 -0500
Date: Fri, 14 Feb 2003 13:48:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Rick Wesson <wessorh@ar.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet-Draft Cutoff Dates for San Francisco, CA
 (March 16-21, 2003)
Message-ID: <410796153.1045230494@p3.JCK.COM>
In-Reply-To: <Pine.LNX.4.33.0302140922440.664-100000@flash.ar.com>
References:  <Pine.LNX.4.33.0302140922440.664-100000@flash.ar.com>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Friday, 14 February, 2003 09:24 -0800 Rick Wesson 
<wessorh@ar.com> wrote:

> Could we see these cutoff dates on the main meeting page,
> since they change and the location of this document isn't well
> know.

Rick,

The Secretariat is almost certainly better at reading minds than 
I am, but I don't quite understand what you want here.   On what 
I think of as the "main meeting page" 
(http://www.ietf.org/meetings/IETF-56.html for this meeting), 
there is a link called "Important Meeting Dates".  It leads to a 
page that has these dates, and the registration cutoffs, etc., 
on it.  Do you think we need:

	(i) To change "Important Meeting Dates" to "Important
	Meeting Dates, including I-D cutoffs"?
	
	(ii) To move some or all of those dates onto the main
	meeting page?  That ought to be possible since neither
	the main meeting page or the referenced one are very
	long.
	
	(iii) To put a note onto the cutoff dates page
	(http://www.ietf.org/meetings/cutoff_dates_56.html) that
	contains all of the prohibitions, threats, and
	explanations about what happens if one misses the
	deadline and when documents can next be submitted from
	the mailing list announcement?   That information hasn't
	changed for years, but it probably should be easier for
	the new and/or forgetful to find.

Just trying to clarify... I don't have any strong opinions about 
this.

      john






From owner-ietf@ietf.org  Fri Feb 14 14:00:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01197;
	Fri, 14 Feb 2003 14:00:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jl4Y-0007Ae-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 14:00:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jl4H-00078z-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 14:00:13 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00806
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:52:57 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18jl0Q-0003Ty-00; Fri, 14 Feb 2003 18:56:14 +0000
Date: Fri, 14 Feb 2003 18:56:12 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Bob Braden <braden@ISI.EDU>
cc: randy@psg.com, "" <tytso@mit.edu>, "" <mrose+mtr.netnews@dbc.mtview.ca.us>,
        "" <ietf@ietf.org>
Subject: Re: movies vs chat logs
In-Reply-To: <200302141732.RAA04670@gra.isi.edu>
Message-ID: <Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk>
References: <200302141732.RAA04670@gra.isi.edu>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.9 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18jl0Q-0003Ty-00*SL9zqbTAQQw* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 14 Feb 2003, Bob Braden wrote:

>   *> working group can often take better minutes than an outsider.  On the
>   *> other hand, it is very hard to take good minutes and/or scribe while
>   *> participating in the discussion, and often the minutes will suffer for
>   *> those portions of the meeting where the minute-taker also wants to
>   *> join into the discussion.  (Or stand in line at the mike, etc.)
>
> In any of the WG meetings I have attended in the last 10 years, it would
> not have been hard to find a person in the room who was not participating
> in the discussion.  In fact, 95-99% of the people in the room were
> non-participants and were therefore potential note takers.

You fail to grasp the fundamentally non-participatory role of the
non-participant.

L.

this the same 95-99% staring blankly at their laptops?

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Fri Feb 14 14:42:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02522;
	Fri, 14 Feb 2003 14:42:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jljC-000162-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 14:42:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jlj2-00014O-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 14:42:20 -0500
Received: from gusto.araneus.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02304;
	Fri, 14 Feb 2003 14:35:03 -0500 (EST)
Received: from guava.araneus.fi (adsl-63-197-0-204.dsl.snfc21.pacbell.net [63.197.0.204])
	by gusto.araneus.fi (8.11.6/8.11.6) with ESMTP id h1EJckZ16109;
	Fri, 14 Feb 2003 11:38:46 -0800 (PST)
Received: (from gson@localhost)
	by guava.araneus.fi (8.11.6/8.11.6) id h1EJckK10941;
	Fri, 14 Feb 2003 11:38:46 -0800 (PST)
Date: Fri, 14 Feb 2003 11:38:46 -0800 (PST)
Message-Id: <200302141938.h1EJckK10941@guava.araneus.fi>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
In-Reply-To: <20030214103228.71052.qmail@cr.yp.to>
References: <200302101659.LAA15654@ietf.org>
	<20030214103228.71052.qmail@cr.yp.to>
X-Mailer: VM 7.04 under Emacs 20.7.1
From: gson@nominum.com (Andreas Gustafsson)
Sender: owner-ietf@ietf.org
Precedence: bulk

D. J. Bernstein writes:
> This ``clarification'' document prohibits several perfectly legitimate,
> very widely deployed, AXFR implementation techniques. See my web page
> http://cr.yp.to/djbdns/axfr-clarify.html for details. In particular,
> this document violates RFC 2119, section 6, in five separate ways.

Your objections are certainly well known by now, and I have repeatedly
responded to them.

> At least seven people have gone on record as objecting to axfr-clarify:
> 
>    Dean Anderson,
>    Len Budney,
>    Felix von Leitner,

Can you please show us that record?  I cannot find any messages from
Felix von Leitner in my namedroppers archive.

>    Kenji Rikitake,

Kenji Rikitake withdrew his objection.

>    Aaron Swartz,

Aaron Swartz' objections appear to be based on his belief that BIND 8
and UltraDNS violate section 3 of the draft.  I have not seen any
further objections from him after I pointed out that they don't.

>    Sam Trenholme (MaraDNS implementor), and
>    me (djbdns implementor).

> Furthermore, the Yokohama minutes report a WG decision that axfr-clarify
> is ``too bind specific''---too specific to BIND 9, to be precise.

My impression (based entirely on a private e-mail discussion with
Randy Bush, since I was not present at the Yokohama meeting) is that
this was not a decision that axfr-clarify is too BIND specific in the
view of the WG, but rather a decision to give the draft more time for
discussion due to *your* claim that it is too BIND specific.
-- 
Andreas Gustafsson, gson@nominum.com



From owner-ietf@ietf.org  Fri Feb 14 15:26:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03776;
	Fri, 14 Feb 2003 15:26:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jmNq-0003rC-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 15:24:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jmNa-0003pb-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 15:24:14 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03516
	for <ietf@ietf.org>; Fri, 14 Feb 2003 15:16:57 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h1EKK9wZ018482;
	Fri, 14 Feb 2003 15:20:09 -0500
Message-Id: <200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6 02/09/2003 with nmh-1.0.4+dev
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
Cc: ietf@ietf.org
Subject: Re: movies vs chat logs 
In-Reply-To: Your message of "Fri, 14 Feb 2003 18:56:12 GMT."
             <Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk> 
References: <200302141732.RAA04670@gra.isi.edu>
            <Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1188100144P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Feb 2003 15:20:09 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1188100144P
Content-Type: text/plain; charset=us-ascii

On Fri, 14 Feb 2003 18:56:12 GMT, Lloyd Wood said:

> You fail to grasp the fundamentally non-participatory role of the
> non-participant.

And the non-participants are there why, exactly? (Note that I'm basically
clueless on this one - there's been a few IETFs that have actually been
plausible for me to attend, but I passed because there weren't any drafts/etc
up for discussion that I felt needed debating...)

I wonder if the number of "tourists" would go down if it became tradition
that if you were sitting there and not actively participating, you could
summarily be drafted to take notes.


--==_Exmh_-1188100144P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+TU94cC3lWbTT17ARAha/AKCzmj1hAJ8o9Tfyf7SQgmfO5ITowQCg5lRk
/dOhOljDU3afkdGaJO35srw=
=0+8N
-----END PGP SIGNATURE-----

--==_Exmh_-1188100144P--



From owner-ietf@ietf.org  Fri Feb 14 15:32:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04058;
	Fri, 14 Feb 2003 15:32:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jmUd-00043R-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 15:31:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jmUN-00041P-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 15:31:15 -0500
Received: from gusto.araneus.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03690;
	Fri, 14 Feb 2003 15:23:56 -0500 (EST)
Received: from guava.araneus.fi (adsl-63-197-0-204.dsl.snfc21.pacbell.net [63.197.0.204])
	by gusto.araneus.fi (8.11.6/8.11.6) with ESMTP id h1EKOkZ16221;
	Fri, 14 Feb 2003 12:24:46 -0800 (PST)
Received: (from gson@localhost)
	by guava.araneus.fi (8.11.6/8.11.6) id h1EKOkS10983;
	Fri, 14 Feb 2003 12:24:46 -0800 (PST)
Date: Fri, 14 Feb 2003 12:24:46 -0800 (PST)
Message-Id: <200302142024.h1EKOkS10983@guava.araneus.fi>
To: Dean Anderson <dean@av8.com>
Cc: Robert Elz <kre@munnari.OZ.AU>, "D. J. Bernstein" <djb@cr.yp.to>,
        <ietf@ietf.org>, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <Pine.LNX.4.44.0302141304410.23971-100000@commander.av8.net>
References: <10697.1045222702@munnari.OZ.AU>
	<Pine.LNX.4.44.0302141304410.23971-100000@commander.av8.net>
X-Mailer: VM 7.04 under Emacs 20.7.1
From: gson@nominum.com (Andreas Gustafsson)
Sender: owner-ietf@ietf.org
Precedence: bulk

Dean Anderson writes:
> I don't think they can be dismissed so easilly. Indeed, I think the
> proposed changes are rather "oddball", and are actually unncessary in
> order to implement IXFR (which was the original claimed justification).

This is not a "change".  There are no existing standards which mandate
or even explicitly allow mixing of data between zones.  On the
contrary, RFC1035 specifically suggests using separate data structures
that ensure that no such mixing occurs:

   6.1.2. Database

   While name server implementations are free to use any internal data
   structures they choose, the suggested structure consists of three major
   parts:

      - A "catalog" data structure which lists the zones available to
	this server, and a "pointer" to the zone data structure.  The
	main purpose of this structure is to find the nearest ancestor
	zone, if any, for arriving standard queries.

      - Separate data structures for each of the zones held by the
	name server.

      - A data structure for cached data. (or perhaps separate caches
	for different classes)

Which one is more "oddball", a server which follows this suggestion or
one which does not?

> Indeed, the proposed changes are only necessary to justify BINDs' oddball
> IXFR changes. They are only necessary to make BIND 9 compliant with the
> RFC's.

BIND 9 is compliant with the existing AXFR standard even without
axfr-clarify.  It's not hard to comply since the existing the
specification is almost nonexistent.

> It seems quite odd that a "clarification" would put 77% of the existing
> servers out of compliance,

77% of the existing servers do not reliably interoperate in IXFR (even
with one another), and sometimes serve data inconsistent between the
authoritative servers of a zone.  They *should* be declared out of
compliance.

> and only brings into compliance a currently
> non-compliant implementation.

Again, BIND 9 is currently compliant.

> Consensus on the part of Bind proponents, yes. Consensus when the wider
> community is counted, no.

I am not a BIND proponent.  Although I wrote the draft while working
on BIND 9, I encountered the interoperability problems caused by the
current lack of specification and saw the need for clarification years
before I received my first BIND-related paycheck.  I currently work on
products that directly compete with BIND, and I have no financial
incentive to see BIND succeed.

I have been reluctant to bring up this issue because because it should
make no difference whatsoever - the draft should be judged solely on
its technical merits, not based on the affiliations of its proponents,
but the groundless accusations of misconduct and conspiracy theories
by you and Dr. Bernstein have gone too far.
-- 
Andreas Gustafsson, gson@nominum.com



From owner-ietf@ietf.org  Fri Feb 14 15:57:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04700;
	Fri, 14 Feb 2003 15:57:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jmui-0005ap-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 15:58:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jmsl-0005Xv-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 15:56:27 -0500
Received: from gusto.araneus.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04563;
	Fri, 14 Feb 2003 15:49:09 -0500 (EST)
Received: from guava.araneus.fi (adsl-63-197-0-204.dsl.snfc21.pacbell.net [63.197.0.204])
	by gusto.araneus.fi (8.11.6/8.11.6) with ESMTP id h1EKqqZ16316;
	Fri, 14 Feb 2003 12:52:52 -0800 (PST)
Received: (from gson@localhost)
	by guava.araneus.fi (8.11.6/8.11.6) id h1EKqq011016;
	Fri, 14 Feb 2003 12:52:52 -0800 (PST)
Date: Fri, 14 Feb 2003 12:52:52 -0800 (PST)
Message-Id: <200302142052.h1EKqq011016@guava.araneus.fi>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: "D. J. Bernstein" <djb@cr.yp.to>, ietf@ietf.org, iesg@ietf.org,
        namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <10697.1045222702@munnari.OZ.AU>
References: <20030214103228.71052.qmail@cr.yp.to>
	<200302101659.LAA15654@ietf.org>
	<10697.1045222702@munnari.OZ.AU>
X-Mailer: VM 7.04 under Emacs 20.7.1
From: gson@nominum.com (Andreas Gustafsson)
Sender: owner-ietf@ietf.org
Precedence: bulk

Robert Elz writes:
> That related to some of the language in the draft I believe (I was there,
> and I think was one of those who supported this position).

Hmm, this seems a bit different from Randy's recollection.  But anyway...

> Some of that
> I still believe could be cleaned up to be nicer.   It doesn't relate to
> any of the substance though, nor particularly to BIND 9, but rather to use
> of terms like "slave" and "master" which are (recent) BIND inventions to
> refer to what the DNS (1034/1035) has always used the words "secondary"
> and "primary" for.

These terms were defined in RFC1996 and are also used in RFC2136, and
they seem clearer than "primary" and "secondary" when describing
topologies where a slave server is itself acting as a master for other
slaves.  If you like, I could add a reference like "This document uses
the terms master and slave as defined in RFC1996".

> There's a bit more like that I think as well.  None
> of it really matters, though the doc would be better if it was all fixed.

I don't recall seeing any specific suggestions for changes, and I did
not attend the Yokohama meeting.  Could you please them to me or
namedroppers?
-- 
Andreas Gustafsson, gson@nominum.com



From owner-ietf@ietf.org  Fri Feb 14 16:48:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06097;
	Fri, 14 Feb 2003 16:48:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jnh6-0006Vg-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 16:48:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jhp5-0004EA-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 10:32:19 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24533
	for <ietf@ietf.org>; Fri, 14 Feb 2003 10:24:35 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: movies vs chat logs
Date: Fri, 14 Feb 2003 09:28:20 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BB15@mail.cynetanetworks.com>
Thread-Topic: movies vs chat logs
Thread-Index: AcLUOxyMmbXaQiJxT6qYDMfVn3XieAAAZgtQ
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA06097

I THINK this is the right e-mail to follow up to...

1. I know I found the JABBER logs for TRIGTRAN to be very useful 
in vetting our minutes (what did we MISS, who really said that, what 
was that person's last name - can't count on this last, but it's 
another pair of eyes in a relatively small community).

2. I've been taking minutes at every session I attend for the
last two or three IETFs, and they've tended to be "he said/she said"
in nature. I've usually gotten thank-yous from working group chairs for
this form of minutes, and I've gotten what-was-the-points from several
other readers. I'm thinking working group chairs would benefit
a lot from video archives, and some readers probably would benefit
from transcripts, but even text transcripts for a five-day, six-or-so-track
meeting aren't THAT easy to blast through - digesting the blow-by-blow
is still the most important ingredient, and the hardest to farm out...

Spencer

> -----Original Message-----
> From: Theodore Ts'o [mailto:tytso@mit.edu]
> Sent: Friday, February 14, 2003 8:47 AM
> To: Randy Bush
> Cc: Marshall Rose; ietf@ietf.org
> Subject: Re: movies vs chat logs
> 
> 
> On Thu, Feb 13, 2003 at 10:33:58PM -0800, Randy Bush wrote:
> > 
> > i have used jabber in ietf meetings and similarcontexts.  it works
> > to coordinate stuff in real-time.  but that was not my application
> > this time.  i really was after the as much content of the meeting
> > as possible.  to do that well in jabber or whatever, one would have
> > to pay a court transcription person.  whereas, as someone already
> > pointed out, a cheap video camera does the job.
> 
> On the other hand, it's much faster and convenient to scan (and
> search) a text transcript compared to viewing a video feed.  It also
> takes up less space to store.  It's extremely amusing to think of a
> scribe as a compression algorithm, but that's basically what's going
> on.  Unfortunately, as always, compression can sometimes be expensive.
> 
> In some cases we might be able to get cheap grad students.  Or perhaps
> we could find people who would be willing to transcribe 2 or 3 wg
> sessions that they aren't otherwise participating in exchange for a
> deep discount on their registration fee?  There would need to be some
> quality control (maybe the wg chair has to certify afterwards that the
> transcript was an accurate record of the proceedings), but it would
> help make much better minutes.
> 
> Of course, there are some downsides to having a non-participant scribe
> or take minutes for a meeting.  Someone who is familiar with the
> background, context, and (unfortunately, sometimes) jargon of a
> working group can often take better minutes than an outsider.  On the
> other hand, it is very hard to take good minutes and/or scribe while
> participating in the discussion, and often the minutes will suffer for
> those portions of the meeting where the minute-taker also wants to
> join into the discussion.  (Or stand in line at the mike, etc.)
> 
> That being said, though, I think that if the scribe was comprehensive
> enough, and the text was then immediately reviewed by the wg chairs
> and other core participants in the meeting, while the discusions was
> still fresh in their minds, the result might be a much *better* record
> of what happened than the current system of taking minutes for the
> meeting.
> 
> 						- Ted
> 
> 
> _______________________________________________
> This message was passed through 
> ietf_censored@carmen.ipv6.cselt.it, which is a sublist of 
> ietf@ietf.org. Not all messages are passed. Decisions on what 
> to pass are made solely by Raffaele D'Albenzio.
> 





From owner-ietf@ietf.org  Fri Feb 14 17:10:06 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06771;
	Fri, 14 Feb 2003 17:10:05 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jo3M-0007ik-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:11:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jhu4-0004Wj-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 10:37:28 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24721
	for <ietf@ietf.org>; Fri, 14 Feb 2003 10:30:13 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Protocol Action: iSCSI to Proposed Standard
Date: Fri, 14 Feb 2003 09:33:59 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BB16@mail.cynetanetworks.com>
Thread-Topic: Protocol Action: iSCSI to Proposed Standard
Thread-Index: AcLUACbma258mCcCRkyzmc61/K2RiAAPbJ8g
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA06771

Loa, I would make this stronger still - the problem as I understood it
was that "transport" is ambiguous (in the world of iSCSI), so even in
the presence of "strong and explicitly stated reasons" to call SCSI 
transport "transport", more IETF reviewers will be confused than
enlightened.

I'd go for a requirement for Internet terminology - SCSI transport
would always be qualified, in this case.

Spencer

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.se]
> Sent: Friday, February 14, 2003 1:43 AM
> To: RJ Atkinson
> Cc: Mallikarjun C.; Bob Braden; sob@harvard.edu; mankin@psg.com;
> ips@ece.cmu.edu; ietf@ietf.org
> Subject: Re: Protocol Action: iSCSI to Proposed Standard
> 
> 
> 
> Ran,
> 
> would agree to this, and put even stronger
> 
> "... Internet RFCs the normal Inernet terminology SHOULD be 
> used, unless 
> there
> are very stong and explicitly stated reasons not to ..."
> 
> it should als  be that the I* have a guiding role in this
> 
> /Loa
> 
> 
> RJ Atkinson wrote:
> 
> >
> > On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, 
> Mallikarjun C. 
> > wrote:
> >
> >>> All the Internet documentation with which I am familiar, 
> as well as the
> >>
> >>
> >> I think we have a case of overlapping vocabulary from two 
> different 
> >> domains.
> >>
> >> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
> >> a "SCSI transport protocol" (as opposed to a SCSI 
> application layer 
> >> protocol).
> >> Parallel SCSI, Fibre Channel etc. are all "SCSI 
> transports" per SCSI 
> >> conventions.
> >> That is all the critiqued abstract is trying to describe.
> >
> >
> > In the context of an *Internet* RFC, it seems sensible to 
> use the normal
> > Internet terminology -- unless one very very clearly 
> indicates that a
> > term is being used in some different semantic.  One might 
> postulate that
> > the document's editors and RFC-Editor could work out a 
> mutually agreeable
> > editorial change here to add clarity.
> >
> > Ran
> >
> >
> >
> >
> 
> 
> 
> _______________________________________________
> This message was passed through 
> ietf_censored@carmen.ipv6.cselt.it, which is a sublist of 
> ietf@ietf.org. Not all messages are passed. Decisions on what 
> to pass are made solely by Raffaele D'Albenzio.
> 





From owner-ietf@ietf.org  Fri Feb 14 17:10:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06797;
	Fri, 14 Feb 2003 17:10:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jo5I-0007jz-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:13:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jkjT-0006UU-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 13:38:43 -0500
Received: from ihemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00009
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:31:27 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1EIZAM27786
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:35:10 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <DVZNXDMM>; Fri, 14 Feb 2003 19:35:09 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64EBE@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Bob Braden <braden@ISI.EDU>, randy@psg.com, tytso@mit.edu
Cc: mrose+mtr.netnews@dbc.mtview.ca.us, ietf@ietf.org
Subject: RE: movies vs chat logs
Date: Fri, 14 Feb 2003 19:34:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf@ietf.org
Precedence: bulk

I have a hard time believing that chat-logs can ever come 
close to a reasonable "report of what happened". That is in
the IETF context. Take a look at all the WG sessions minutes
and try to see for yourself if they are understandable for
anyone who was not present? And those get posted and
reviewed and edited before they get sent to minutes@ietf.org.

Thanks,
Bert 





From owner-ietf@ietf.org  Fri Feb 14 17:11:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06870;
	Fri, 14 Feb 2003 17:11:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jo5J-0007k5-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:13:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jkla-0006Ys-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 13:40:54 -0500
Received: from lucy.trebia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00041
	for <ietf@ietf.org>; Fri, 14 Feb 2003 13:33:32 -0500 (EST)
Received: by lucy with Internet Mail Service (5.5.2653.19)
	id <1YNVYA59>; Fri, 14 Feb 2003 13:37:11 -0500
Message-ID: <63616B261CEFD411834D00D0B7A86CF701BA4E8B@lucy>
From: "David J. Brown" <david.brown@trebia.com>
To: "'Loa Andersson'" <loa@pi.se>, RJ Atkinson <rja@extremenetworks.com>
Cc: "Mallikarjun C." <cbm@rose.hp.com>, Bob Braden <braden@ISI.EDU>,
        sob@harvard.edu, mankin@psg.com, ips@ece.cmu.edu, ietf@ietf.org
Subject: RE: Protocol Action: iSCSI to Proposed Standard
Date: Fri, 14 Feb 2003 13:37:08 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: owner-ietf@ietf.org
Precedence: bulk

The document uses the term "transport" correctly.  

Chapter 1, from which the sentences in the mail message were drawn, clearly
states that the term transport refers to a "SCSI transport", a phrase which
it defines accurately.  The mail message did omit several sentences from
Chapter 1, including the sentences that defined "SCSI transport" and made it
clear that that's the kind of transport under discussion in the offending
sentence.  Perhaps it should have included the whole chapter verbatim.

Are you objecting to the actual document, namely
draft-ietf-ips-iscsi-20.pdf, or only to the mail message that accompanied
it?

dj

> In the context of an *Internet* RFC, it seems sensible to use the normal
> Internet terminology -- unless one very very clearly indicates that a
> term is being used in some different semantic.

-----Original Message-----
From: Loa Andersson [mailto:loa@pi.se]
Sent: Friday, February 14, 2003 2:43 AM
To: RJ Atkinson
Cc: Mallikarjun C.; Bob Braden; sob@harvard.edu; mankin@psg.com;
ips@ece.cmu.edu; ietf@ietf.org
Subject: Re: Protocol Action: iSCSI to Proposed Standard



Ran,

would agree to this, and put even stronger

"... Internet RFCs the normal Inernet terminology SHOULD be used, unless 
there
are very stong and explicitly stated reasons not to ..."

it should als  be that the I* have a guiding role in this

/Loa


RJ Atkinson wrote:

>
> On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, Mallikarjun C. 
> wrote:
>
>>> All the Internet documentation with which I am familiar, as well as the
>>
>>
>> I think we have a case of overlapping vocabulary from two different 
>> domains.
>>
>> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
>> a "SCSI transport protocol" (as opposed to a SCSI application layer 
>> protocol).
>> Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI 
>> conventions.
>> That is all the critiqued abstract is trying to describe.
>
>
> In the context of an *Internet* RFC, it seems sensible to use the normal
> Internet terminology -- unless one very very clearly indicates that a
> term is being used in some different semantic.  One might postulate that
> the document's editors and RFC-Editor could work out a mutually agreeable
> editorial change here to add clarity.
>
> Ran
>
>
>
>





From owner-ietf@ietf.org  Fri Feb 14 17:12:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06940;
	Fri, 14 Feb 2003 17:12:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jo5J-0007kX-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:13:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jl11-00073U-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 13:56:51 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00716;
	Fri, 14 Feb 2003 13:49:35 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id NAA05683;
	Fri, 14 Feb 2003 13:46:55 -0500
Date: Fri, 14 Feb 2003 13:48:09 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Robert Elz <kre@munnari.OZ.AU>
cc: "D. J. Bernstein" <djb@cr.yp.to>, <ietf@ietf.org>, <iesg@ietf.org>,
        <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <10697.1045222702@munnari.OZ.AU>
Message-ID: <Pine.LNX.4.44.0302141304410.23971-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Fri, 14 Feb 2003, Robert Elz wrote:

>     Date:        14 Feb 2003 10:32:28 -0000
>     From:        "D. J. Bernstein" <djb@cr.yp.to>
>     Message-ID:  <20030214103228.71052.qmail@cr.yp.to>
>
>   | This ``clarification'' document prohibits several perfectly legitimate,
>   | very widely deployed, AXFR implementation techniques.
>
> It prohibits some odd-ball techniques that risk future enhancements
> (and generally clarifies the almost non-existant specification).

I don't think they can be dismissed so easilly. Indeed, I think the
proposed changes are rather "oddball", and are actually unncessary in
order to implement IXFR (which was the original claimed justification).

Indeed, the proposed changes are only necessary to justify BINDs' oddball
IXFR changes. They are only necessary to make BIND 9 compliant with the
RFC's.

It seems quite odd that a "clarification" would put 77% of the existing
servers out of compliance, and only brings into compliance a currently
non-compliant implementation.  I think it is unprecedented in the history
of any standards organization, not just the IETF.  Such a significant
change is clearly a completely new version.  Thus the widespread
complaints about fraudulent labeling and discription of the proposal.

** 45% Bind 8
** 23% Bind 9
** 77% are not bind 9, and will not be compliant after this
"clarification"

This is not the way to run a railroad. (or rather, it is a railroading of
the changes through the process...)

>   | Despite this decision and these extensive objections, the WG chairs
>   | declared ``consensus'' for axfr-clarify and sent it to the IESG.
>
> I believe rough consensus exists on this one (it is rough, but there's
> certainly much more support than opposition).

Consensus on the part of Bind proponents, yes. Consensus when the wider
community is counted, no.

>   | A review of all of the axfr-clarify discussions in the WG list archive
>   | shows that this document is being pushed primarily by people who have
>   | been paid for BIND work:
>
> Even if this were true (and I don't believe it is - I have never been
> paid for any BIND work) it is irrelevant.   It is not at all unusual
> for a group of related people (sometimes all actually currently employed
> by one organisation) to push a proposal.

Of course not. It happens frequently in consortia.  However, a "bloc"
behind a single vendor is usually counted as such.  Its not unheard of for
a vendor to try to create an appearance of widespread support using
subcontactors, when in fact there is none.  When that happens, people cry
"foul". We are crying "foul" now.

>   | Note that the users attacked by this document include BIND 8 users---who
>   | are no longer represented in the WG by implementors, now that the BIND
>   | implementors are pushing BIND 9. The document's proponents admit that
>   | their ``clarification'' imposes rules disobeyed by BIND 8. My survey
>   | http://cr.yp.to/surveys/dns1.html two months ago showed that 45% of all
>   | .com names were served by BIND 8, while only 23% were served by BIND 9.
>
> What has this to do with anything?   All that is being done here is to
> tighten up the specification for how AXFR is supposed to be done.   That
> old BIND code has bugs can hardly be news (even older BIND code had
> millions of bugs).   Nothing proposed is going to cause failures of
> any existing implementations, nor any current implementations to fail to
> interoperate with any new implementations that follow this clarification.

We have hashed this through many, many times, I fail to see how you can
still make this claim with a straight face.  It certainly will cause
failures: It will cause all non-bind 9implementations to be non-compliant
(or 77% of the servers).

> The scare mongering about "huge redeployment costs" is utter nonsense,
> no-one is being asked to redeploy anything.

Asked? No. It is demanded.  This is a change to a standard, and to be
compliant demands conformance to the standard, and thus change, and
redeployment.

Perhaps unfortunately, the IETF has no branding program. However, we still
have interoperability testing to determine compliance with the standard.

> All this document seeks to do is to get future AXFR implementations to
> be a little tighter in what they do, so that some possible (even worse)
> implementations bugs would have less bad effects than they might otherwise
> have done.

Clarification is a worthy goal. No one is opposed to clarification.
However, the changes proposed go in the wrong direction, and are motivated
purely by a crufty IXFR implementation in Bind 9.  Many people have
indicated that the correct approch to clarification is to look at what
Bind8 and _OTHER IMPLEMENTATIONS_ did.

Since BIND9 is described in an Oreily book, this could be a difficult for
them. However, they should have thought about that before publishing a
book describing non-conforming implmentation as though it was standards
compliant. They created their own mess, and now want 77% of the world to
fix it for them. Talk about the shifting of costs to someone else...

The Bind9 people claim the changes are necessary to support IXFR. Of
course these changes aren't necessary. IXFR is in principle no different
than database transaction log processing. It has no bearing whatsoever on
AXFR any more than Oracle incremental replication has bearing on the
Oracle query protocol.  They made changes to AXFR to make their crufty
IXFR implementation work, because they are bad engineers. They exercised
even worse judgement by publishing a book on their implementation prior to
standardization. Now they want the 77% of the world to jump through hoops
to make their oddball, badly engineered work "standard".

I'm not buying it.

> The effect upon your implementation would be, that unless you alter
> your implementation, you wouldn't be able to claim that it is conformant
> with this new RFC (once it is issued of course).   That's it.   As you
> seem to dislike AXFR as a zone transfer mechanism anyway (which is just
> fine, it has never been required) I'm not sure why you'd care.

That's huge.  And its not _only_ djbdns.

		--Dean







From owner-ietf@ietf.org  Fri Feb 14 17:13:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07096;
	Fri, 14 Feb 2003 17:13:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jo5K-0007kd-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:13:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jlwH-0001yj-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 14:56:01 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02793
	for <ietf@ietf.org>; Fri, 14 Feb 2003 14:48:43 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: movies vs chat logs
Date: Fri, 14 Feb 2003 13:52:26 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F55C3742@mail.cynetanetworks.com>
Thread-Topic: movies vs chat logs
Thread-Index: AcLUU/pC73IVXuRPQjq/5o3sqweEywABZcHA
From: "Spencer Dawkins" <sdawkins@cynetanetworks.com>
To: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA07096

I've asked to do so a few times in the IETF, 
but I've been allowed to put myself "virtually" in 
line for the mike, when I'm taking notes for a 
working group, so I can keep typing. 

Then all I have to do is figure out what *I* said later...

Spencer

> -----Original Message-----
> From: Bob Braden [mailto:braden@ISI.EDU]
> Sent: Friday, February 14, 2003 11:33 AM
> To: randy@psg.com; tytso@mit.edu
> Cc: mrose+mtr.netnews@dbc.mtview.ca.us; ietf@ietf.org
> Subject: Re: movies vs chat logs
> 
> 
> 
>   *> working group can often take better minutes than an 
> outsider.  On the
>   *> other hand, it is very hard to take good minutes and/or 
> scribe while
>   *> participating in the discussion, and often the minutes 
> will suffer for
>   *> those portions of the meeting where the minute-taker 
> also wants to
>   *> join into the discussion.  (Or stand in line at the mike, etc.)
> 
> In any of the WG meetings I have attended in the last 10 
> years, it would
> not have been hard to find a person in the room who was not 
> participating
> in the discussion.  In fact, 95-99% of the people in the room were
> non-participants and were therefore potential note takers.
> 
> Bob Braden





From owner-ietf@ietf.org  Fri Feb 14 17:26:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07559;
	Fri, 14 Feb 2003 17:26:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18joIs-0001G0-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:27:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18joIe-0001Df-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 17:27:16 -0500
Received: from sopacsun.fig.net.fj (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07439
	for <ietf@ietf.org>; Fri, 14 Feb 2003 17:19:45 -0500 (EST)
Received: from [192.168.0.253] (unknown [202.62.1.33])
	by sopacsun.fig.net.fj (Postfix) with ESMTP id C7C4CAAB57
	for <ietf@ietf.org>; Fri, 14 Feb 2003 17:22:36 -0500 (EST)
Subject: Re: movies vs chat logs
From: Franck Martin <franck@sopac.org>
To: ietf@ietf.org
In-Reply-To: <200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
References: <200302141732.RAA04670@gra.isi.edu>
	<Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk> 
	<200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
Content-Type: multipart/alternative; boundary="=-U0N9aidsz03slOsAUzTA"
X-Mailer: Ximian Evolution 1.0.8-3mdk 
Date: 15 Feb 2003 10:22:25 +1200
Message-Id: <1045261357.2759.1.camel@franck-lxnb>
Mime-Version: 1.0
Sender: owner-ietf@ietf.org
Precedence: bulk


--=-U0N9aidsz03slOsAUzTA
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I was wondering if a speech to text software like dragonspeaking could
be the scribe and output to jabber?

Also audio streaming is quite good (low bandwidth) and you can listen to
it like the radio...

Cheers

--=-U0N9aidsz03slOsAUzTA
Content-Type: text/html; charset=utf-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/1.0.4">
</HEAD>
<BODY>
I was wondering if a speech to text software like dragonspeaking could be the scribe and output to jabber?
<BR>

<BR>
Also audio streaming is quite good (low bandwidth) and you can listen to it like the radio...
<BR>

<BR>
Cheers
</BODY>
</HTML>

--=-U0N9aidsz03slOsAUzTA--




From owner-ietf@ietf.org  Fri Feb 14 17:38:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07983;
	Fri, 14 Feb 2003 17:38:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18joUT-0001pe-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 17:39:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18joTU-0001nq-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 17:38:28 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07644;
	Fri, 14 Feb 2003 17:31:09 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h1EMYOwZ011558;
	Fri, 14 Feb 2003 17:34:24 -0500
Message-Id: <200302142234.h1EMYOwZ011558@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6 02/09/2003 with nmh-1.0.4+dev
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: Your message of "Fri, 14 Feb 2003 13:48:09 EST."
             <Pine.LNX.4.44.0302141304410.23971-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0302141304410.23971-100000@commander.av8.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1163900064P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Feb 2003 17:34:24 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-1163900064P
Content-Type: text/plain; charset=us-ascii

On Fri, 14 Feb 2003 13:48:09 EST, Dean Anderson said:

> It seems quite odd that a "clarification" would put 77% of the existing
> servers out of compliance, and only brings into compliance a currently
> non-compliant implementation.  I think it is unprecedented in the history
> of any standards organization, not just the IETF.  Such a significant
> change is clearly a completely new version.  Thus the widespread
> complaints about fraudulent labeling and discription of the proposal.

Granted, it's only a BCP, but see RFC2505.  A large percentage of
implementations were non-conforming to THAT too - but the situation has
improved dramatically since then.  And note that there are more servers
for *THAT* protocol, from more vendors, than for DNS.


-- 
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech


--==_Exmh_-1163900064P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+TW7wcC3lWbTT17ARAuo3AKDtwRSE4qMVt3OXFiiCrZ64OjB7kACdHLq2
dkIUTf6PLSDDbiorG0+QJxE=
=QnwB
-----END PGP SIGNATURE-----

--==_Exmh_-1163900064P--



From owner-ietf@ietf.org  Fri Feb 14 18:24:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09118;
	Fri, 14 Feb 2003 18:24:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jpBa-0002s4-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 18:24:02 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jp9q-0002om-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 18:22:14 -0500
Received: from boromir.vpop.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09028
	for <ietf@ietf.org>; Fri, 14 Feb 2003 18:14:54 -0500 (EST)
Received: from [192.168.0.10] (ppp-67-118-246-213.dialup.pltn13.pacbell.net [67.118.246.213])
	by boromir.vpop.net (Postfix) with ESMTP
	id 9C20B3A60CF; Fri, 14 Feb 2003 15:18:37 -0800 (PST)
Mime-Version: 1.0
Message-Id: <a05111b0bba7329a4a534@[192.168.0.10]>
In-Reply-To: <1045261357.2759.1.camel@franck-lxnb>
References: <200302141732.RAA04670@gra.isi.edu>
 <Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk> 
 <200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
 <1045261357.2759.1.camel@franck-lxnb>
Date: Fri, 14 Feb 2003 15:18:34 -0800
To: Franck Martin <franck@sopac.org>, ietf@ietf.org
From: Ari Ollikainen <Ari@OLTECO.com>
Subject: Re: movies vs chat logs
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:22 AM +1200 2/15/03, Franck Martin wrote:
>I was wondering if a speech to text software like dragonspeaking could be the scribe and output to jabber?

	Dream on...


 
           +----------------------------------------------+
           | You need only two tools: WD-40 and duct tape.|
           | If it doesn't move and it should, use WD-40. |
           | If it moves and shouldn't, use duct tape.    |
           +----------------------------------------------+




From owner-ietf@ietf.org  Fri Feb 14 19:31:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10494;
	Fri, 14 Feb 2003 19:31:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jqBw-0004hS-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 19:28:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jq8D-0004fO-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 19:24:37 -0500
Received: from bs.jck.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10284
	for <ietf@ietf.org>; Fri, 14 Feb 2003 19:17:18 -0500 (EST)
Received: from [209.187.148.215] (helo=p3.JCK.COM)
	by bs.jck.com with esmtp (Exim 4.10)
	id 18jq4h-000FlK-00; Fri, 14 Feb 2003 19:20:59 -0500
Date: Fri, 14 Feb 2003 19:20:59 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: movies vs chat logs
Message-ID: <15903888.1045250459@p3.JCK.COM>
In-Reply-To: <200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
References: <200302141732.RAA04670@gra.isi.edu>           
 <Pine.GSO.4.50.0302141854140.25996-100000@artemis.ee.surrey.ac.uk>
  <200302142020.h1EKK9wZ018482@turing-police.cc.vt.edu>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Friday, 14 February, 2003 15:20 -0500 
"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu> wrote:

> I wonder if the number of "tourists" would go down if it
> became tradition that if you were sitting there and not
> actively participating, you could summarily be drafted to take
> notes.

Been tried.  On average, it produces really poor notes, or notes 
that don't get submitted.

If one wants decent notes, one really needs a willing volunteer 
or at least someone who feels committed to the job.  Some 
tourists might feel obligated enough if tapped, but experience 
in the IETF and other organizations suggests that one should not 
bet on it.

   john





From owner-ietf@ietf.org  Fri Feb 14 22:10:34 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13331;
	Fri, 14 Feb 2003 22:10:34 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jshk-0002A8-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 22:09:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jshW-00029Y-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 22:09:15 -0500
Received: from kcmso2.proxy.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13192
	for <ietf@ietf.org>; Fri, 14 Feb 2003 22:01:53 -0500 (EST)
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h1F35dXR009790
	for <ietf@ietf.org>; Fri, 14 Feb 2003 21:05:40 -0600 (CST)
Received: from att.com (<unknown.domain>[135.210.120.12])
          by maillennium.att.com (mailgw1) with SMTP
          id <20030215030502gw100kscqje>
          (Authid: tony);
          Sat, 15 Feb 2003 03:05:02 +0000
Message-ID: <3E4DAA72.9030808@att.com>
Date: Fri, 14 Feb 2003 21:48:18 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: movies vs chat logs
References: <9255B6CD76A88943A3062F7D4E6432F543BB15@mail.cynetanetworks.com>
In-Reply-To: <9255B6CD76A88943A3062F7D4E6432F543BB15@mail.cynetanetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a couple of WGs, the person taking notes did so live on the jabber 
channel. A number of times there were corrections made in real time to 
the notes by the other participants. There were also a few cases where 
the note taker would put out a question about something that had just 
happened or been said, and gotten immediate info about his/her question. 
It was also useful when a side conversation occurred and you needed to 
catch back up with what the mike speaker had said.

	Tony Hansen
	tony@att.com




From owner-ietf@ietf.org  Fri Feb 14 22:27:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13552;
	Fri, 14 Feb 2003 22:27:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jt16-0002hv-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 22:29:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jsxW-0002fs-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 22:25:46 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13433
	for <ietf@ietf.org>; Fri, 14 Feb 2003 22:18:24 -0500 (EST)
Received: (qmail 81432 invoked by uid 1016); 15 Feb 2003 03:22:36 -0000
Date: 15 Feb 2003 03:22:36 -0000
Message-ID: <20030215032236.81431.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: axfr-notes.html
References: <200302101659.LAA15654@ietf.org> <20030214103228.71052.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

It has become clear that the BIND company's ``AXFR clarifications'' are
never going to turn into an honest description of the AXFR protocol.

Consequently, for the sake of interoperability, I sat down after my last
message and wrote a web page saying how AXFR actually works:

   http://cr.yp.to/djbdns/axfr-notes.html

Comments are welcome from anyone who wants to help future implementors.
Comments are not welcome from people who are demanding (for commercial
reasons or for religious reasons) that most of the DNS servers on the
Internet be changed to imitate BIND 9.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 14 22:34:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14002;
	Fri, 14 Feb 2003 22:34:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jt6y-000375-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 22:35:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jt6J-0002sU-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 22:34:51 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13585
	for <ietf@ietf.org>; Fri, 14 Feb 2003 22:27:29 -0500 (EST)
Received: (qmail 82624 invoked by uid 1016); 15 Feb 2003 03:31:41 -0000
Date: 15 Feb 2003 03:31:41 -0000
Message-ID: <20030215033141.82623.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030214103228.71052.qmail@cr.yp.to> <200302101659.LAA15654@ietf.org> <10697.1045222702@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Robert Elz writes:
> It prohibits some odd-ball techniques

You are talking about a draft disobeyed by MOST DNS SERVERS ON THE NET.
Please drop the loaded terminology.

> "Violating" 2119 is a nonsense concept.

RFC 2119, section 6: ``Imperatives of the type defined in this memo must
be used with care and sparingly.  In particular, they MUST only be used
where it is actually required for interoperation or to limit behavior
which has potential for causing harm (e.g., limiting retransmisssions)
For example, they must not be used to try to impose a particular method
on implementors where the method is not required for interoperability.''

Contrary to your claims, these are not mere ``recommendations.'' This
draft claims to be following RFC 2119, but blatantly violates RFC 2119,
by trying to impose BIND 9's private decisions on everyone else.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 14 22:43:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14383;
	Fri, 14 Feb 2003 22:43:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jtFe-0004Um-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 22:44:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jtFY-0004Tr-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 22:44:24 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14090
	for <ietf@ietf.org>; Fri, 14 Feb 2003 22:37:02 -0500 (EST)
Received: (qmail 84062 invoked by uid 1016); 15 Feb 2003 03:41:14 -0000
Date: 15 Feb 2003 03:41:14 -0000
Message-ID: <20030215034114.84061.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <200302142024.h1EKOkS10983@guava.araneus.fi> <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net> <200302150157.h1F1vXw11389@guava.araneus.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Andreas Gustafsson writes:
> To both me and the BIND 9 team, it was the obvious design, and the
> BIND 8 behavior was an obvious implementation bug.

To me, the djbdns cache structure is the obvious design, and BIND's
continuing tree-related cache performance problems---all of which are
visible to clients on the wire---are obvious implementation bugs.

Do you think I should write drafts specifying my cache structure,
falsely label those drafts as ``clarifications,'' and pay a bunch of
people to push those drafts through the IETF standardization process?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 14 23:35:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15054;
	Fri, 14 Feb 2003 23:35:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ju22-0005hv-00
	for ietf-list@ran.ietf.org; Fri, 14 Feb 2003 23:34:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ju0W-0005gM-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 23:32:56 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14954
	for <ietf@ietf.org>; Fri, 14 Feb 2003 23:25:34 -0500 (EST)
Received: (qmail 95102 invoked by uid 1016); 15 Feb 2003 04:29:44 -0000
Date: 15 Feb 2003 04:29:44 -0000
Message-ID: <20030215042944.95101.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <200302101659.LAA15654@ietf.org> <20030214103228.71052.qmail@cr.yp.to> <20030214135155.GA8342@outpost.ds9a.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

bert hubert writes:
> Much of your criticism boils down to the fact that you do not have a
> zone concept and do not want to have one, where 1034 and 1035 simply
> ooze with zone definitions and they are clearly part of the DNS philosophy.

It's amazing how many errors you can pack into one paragraph. Facts:

   * My software has zones. It simplifies them for the user, by taking
     advantage of the RFC 1034 database-consistency requirements.

   * The relevant difference between my software and BIND 9 is that,
     when my software sees some of the RFC-1034-violating zones allowed
     by BIND 9, it boils them down to the RFC-1034-compliant parts.

   * BIND 8 does this to some extent too. It would sound pretty stupid
     of you to claim that BIND 8 doesn't ``have a zone concept,'' don't
     you think?

   * The BIND company's ``AXFR clarifications'' try to eliminate the
     RFC 1034 database-consistency requirements, allowing data for the
     same class+name+type to vary across zones, contrary to RFC 1034,
     sections 4.2.1 and 4.2.2.

Furthermore, this zone mismanagement is only one of many problems with
axfr-clarify.

If you decided to imitate BIND 9's database format in your software,
feel free---but stop trying to force me to do the same thing. It isn't
what my users want, and it's not necessary for interoperability.

  [ removing duplicates ]
> Yes, you could build sophisticated hashes & stuff

Learn to program: ``sort -u''.

As for your suggestion to shift this programming burden to the server:
You aren't thinking straight. There will be BIND 8 servers for the
foreseeable future, so you'll have to continue removing duplicates for
the foreseeable future. You'll be imposing a burden on servers without
removing it from clients. Silly.

> I do like to have the ability to add TSIGs to an AXFR in the additional
> section, even if that potentially breaks older remotes.

Again, you aren't thinking straight. Servers don't randomly use TSIG;
they use it _upon request_. Random use of TSIG has no benefits; it's a
pointless incompatibility, and there's no reason to allow it. (Besides,
IPSEC does a better job than TSIG.)

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Sat Feb 15 01:17:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16621;
	Sat, 15 Feb 2003 01:17:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jvcj-0007YU-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 01:16:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jvaz-0007Wt-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 01:14:41 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16478;
	Sat, 15 Feb 2003 01:07:13 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1F6Akd6028212;
	Sat, 15 Feb 2003 17:10:46 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302150610.h1F6Akd6028212@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "15 Feb 2003 04:29:44 -0000."
             <20030215042944.95101.qmail@cr.yp.to> 
Date: Sat, 15 Feb 2003 17:10:46 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> bert hubert writes:
> > Much of your criticism boils down to the fact that you do not have a
> > zone concept and do not want to have one, where 1034 and 1035 simply
> > ooze with zone definitions and they are clearly part of the DNS philosophy.
> 
> It's amazing how many errors you can pack into one paragraph. Facts:
> 
>    * My software has zones. It simplifies them for the user, by taking
>      advantage of the RFC 1034 database-consistency requirements.

	Your software (and BIND 8) causes operational problems by not
	preserving zone contents.

	By incorrectly merging data from child zones you can prevent
	a master from sending correct data.  You can also prevent slaves
	from sending the correct information.  You require administators
	to worry about silly timing issues.  You require administators to
	detect when the timing was wrong and update the serial numbers
	on zones just to get it retransfered with the original information
	because the server couldn't keep the zone contents seperate.

	Senario 1.

	Server 1 master for example.com and slave for division.example.com.
	division.example.com has been updated on it master to have
	new delegation information, the zone has not yet refreshed
	on server 1 for some reason.  You receive email with the
	new delegation information.  You update example.com adjusting
	its serial.  You reload example.com.  You expect the new
	delegation to be advertised in the outgoing zone transfer.
	This doesn't happen because the server messed with the zone
	contents.

	Senario 2.

	Server 1 master example.com
	Server 2 master division.example.com
	Server 3 slave example.com and division.example.com
	Server 4 slave example.com using server 3 as a master.

	Server 2 the delgation infomation for division.example.com is
	update and the parent zone is informed.   Server 1 is updated
	to contain the new delegation information.  Server 3 receives
	the updated parent zone before the updated child zone and
	notifies Server 4 which transfers example.com WITH THE OLD
	DELEGATION INFORMATION.  Both masters were updated to have
	the new delegation information but it doesn't get distributed
	to all the servers.

	You want the IETF to believe that this is *correct* AXFR
	behaviour.  This doesn't pass the giggle test.
	
	This is a common implemention error caused by trying to
	stuff all zones into a common database.  BIND 4 got it
	wrong.  BIND 8 got it wrong.

	You want us all to keep repeating this mistake.

	All that is being asked is that the data in AXFR is preserved
	so that it can be used as the data source of another AXFR and
	as a dataset to which IXFR deltas can be applied.  If you want
	to merge the zones for non AXFR requests go ahead.

	In otherwords what is entered as the zone data is what is
	transmitted as the zone data.

	I was very much aware of this issue when I was working as
	a systems administrator for CSIRO years before I started
	working for ISC.  We had to make regular sweeps of the the
	CSIRO.AU heirarchy to detect and clean up the errors caused
	by nameservers incorrectly merging zone contents.  I got
	very tired of having to explain to all of the different
	system admins what the problem was and how to "fix it" by
	incrementing the serial number and getting the zone
	re-transfered.

	Mark

>    * The relevant difference between my software and BIND 9 is that,
>      when my software sees some of the RFC-1034-violating zones allowed
>      by BIND 9, it boils them down to the RFC-1034-compliant parts.
> 
>    * BIND 8 does this to some extent too. It would sound pretty stupid
>      of you to claim that BIND 8 doesn't ``have a zone concept,'' don't
>      you think?
> 
>    * The BIND company's ``AXFR clarifications'' try to eliminate the
>      RFC 1034 database-consistency requirements, allowing data for the
>      same class+name+type to vary across zones, contrary to RFC 1034,
>      sections 4.2.1 and 4.2.2.
> 
> Furthermore, this zone mismanagement is only one of many problems with
> axfr-clarify.
> 
> If you decided to imitate BIND 9's database format in your software,
> feel free---but stop trying to force me to do the same thing. It isn't
> what my users want, and it's not necessary for interoperability.
> 
>   [ removing duplicates ]
> > Yes, you could build sophisticated hashes & stuff
> 
> Learn to program: ``sort -u''.
> 
> As for your suggestion to shift this programming burden to the server:
> You aren't thinking straight. There will be BIND 8 servers for the
> foreseeable future, so you'll have to continue removing duplicates for
> the foreseeable future. You'll be imposing a burden on servers without
> removing it from clients. Silly.
> 
> > I do like to have the ability to add TSIGs to an AXFR in the additional
> > section, even if that potentially breaks older remotes.
> 
> Again, you aren't thinking straight. Servers don't randomly use TSIG;
> they use it _upon request_. Random use of TSIG has no benefits; it's a
> pointless incompatibility, and there's no reason to allow it. (Besides,
> IPSEC does a better job than TSIG.)
> 
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Sat Feb 15 03:27:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28456;
	Sat, 15 Feb 2003 03:27:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jxeX-0001P6-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 03:26:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jxe8-0001OF-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 03:26:04 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28339;
	Sat, 15 Feb 2003 03:18:37 -0500 (EST)
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1F8MHq18608;
	Sat, 15 Feb 2003 15:22:18 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1F8Kkb14158;
	Sat, 15 Feb 2003 15:20:48 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Dean Anderson <dean@av8.com>
cc: Andreas Gustafsson <gson@nominum.com>, "D. J. Bernstein" <djb@cr.yp.to>,
        ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net> 
References: <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 15 Feb 2003 15:20:46 +0700
Message-ID: <14156.1045297246@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Fri, 14 Feb 2003 17:25:40 -0500 (EST)
    From:        Dean Anderson <dean@av8.com>
    Message-ID:  <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net>

  | 
  | On Fri, 14 Feb 2003, Andreas Gustafsson wrote:
  | > RFC1035 specifically suggests using separate data structures
  | > that ensure that no such mixing occurs:
  | 
  | The key word is "suggests", which has the meaning...

exactly what you think it does - but note, the suggestion relates to
an implementation technique, which certainly isn't going to be required.
Implementors are free to implement however they desire, as long as they
achieve the objective.

Now ask yourself why 1035 would bother even suggesting an implementation
technique.

Don't you think it entirely possible that it is because the requirement
(that which was to be implemented) is so fundamental to the design of
the DNS, that some kind of suggestion of how to actually comply with the
design was worth making?

Implementation methods are often "suggested" in circumstances like that.
That is, when it seems plausible that implementors might miss an important
point and just do it the "easy way", it is common for the spec to indicate
how the implementation can achieve the desired result - this way implementors
either just blindly copy the suggestion, or at least should think about
why they're doing it a different way, and ask themselves if their results
will be the same as the suggested method.

  | No. This isn't true either.  If we clarify AXFR to standardize the
  | _assumptions_ identically and concretely made by many implementors over a
  | long period of time,

I can absolutely guarantee to you that that will never happen.  No-one is
going to standardise a protocol that essentially says "send whatever data
you feel like sending, and believe whatever the other end sends you
without question" which is exactly what the early implementations did.

When we standardise something, we want to first be as sure as we can be
that the protocol is correct for its purpose.  We aren't always very good
at that, but that should certainly be a major aim - documenting something
that doesn't work is a waste of everyone's time.   AXFR as it has been
commonly implemented simply doesn't work reliably.

kre




From owner-ietf@ietf.org  Sat Feb 15 03:42:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28789;
	Sat, 15 Feb 2003 03:42:22 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18jxvx-00020B-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 03:44:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jxvt-0001zJ-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 03:44:25 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28666;
	Sat, 15 Feb 2003 03:36:54 -0500 (EST)
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1F8eTq19209;
	Sat, 15 Feb 2003 15:40:30 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1F8cjb14482;
	Sat, 15 Feb 2003 15:38:45 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <20030215042944.95101.qmail@cr.yp.to> 
References: <20030215042944.95101.qmail@cr.yp.to>  <200302101659.LAA15654@ietf.org> <20030214103228.71052.qmail@cr.yp.to> <20030214135155.GA8342@outpost.ds9a.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Sat, 15 Feb 2003 15:38:45 +0700
Message-ID: <14480.1045298325@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA28789

    Date:        15 Feb 2003 04:29:44 -0000
    From:        "D. J. Bernstein" <djb@cr.yp.to>
    Message-ID:  <20030215042944.95101.qmail@cr.yp.to>

  |    * The BIND company's ``AXFR clarifications'' try to eliminate the
  |      RFC 1034 database-consistency requirements, allowing data for the
  |      same class+name+type to vary across zones, contrary to RFC 1034,
  |      sections 4.2.1 and 4.2.2.

Most of your arguments aren't worth replying to.   This one looks like
it has merit on first glance.   But when examined closely it doesn't.

The database consistency requirements in 1034 *have* to be requirements
imposed upon the operators of the DNS, not the software, as there is
no mechanism in existence which allows the software to ensure this
consistency.

The issue here is "glue" records copied into a parent zone from a child.

If the parent and child are in the same server, the software is able to
ensure that the glue records in the parent are identical to what is in
the child zone - that's what early BIND software did, and I am guessing
that is what your server does.   From a naïve point of view, this looks
to be a good thing.

On the other hand, if the parent and child are operating in different
servers then there's nothing that causes the glue in the parent to be
the same as the records in the child - I have long wished that there
could be (by having the parent actually go query the child, repeatedly)
but for scaling and other reasons, it simply wouldn't work.

Now for your average query this turns out to not matter (which is how
BIND got away with being broken for so long) - a query to a server that
holds both zones will receive its answer using the data that is the child
zone (the zone that actually holds the record in question, or the nearest
parent of that) and so will (assuming the query requests it, one way or
another) get the data (which is glue in the parent) from the child zone.
A query addressed to a parent which doesn't also hold the child zone will
get the glue as added in the parent zone, unaffected by whatever might be
in the child.

Well - most of the time.   And this is where the problems arise, and why
AXFR is relevant to all of this.   If the server for only the parent
did a zone transfer from the server that is also a server for the child
zone, then (using the zone smashing style of earlier BIND) the transfer
it gets contains the records from the child zone, instead of what was
actually configured into the parent zone.

On the other hand, a different server for the parent zone alone, which
did its AXFR from a server that was configured with the parent zone data
and had never seen the child zone (or is a server configured manually
itself, with only the parent zone), would have only the configured glue.

Now we have two servers for the parent only, giving out different answers,
from the same zone, with the same serial number.   That's simply
unacceptable, and wrong, and always has been.   Early BIND had even worse
problems in this area, but they're not relevant here - except that I
certainly hope that no-one is going to come out of the woodwork and
say that because (10 years ago) 99% of the nameservers were running BIND4
that the DNS specs must be "clarified" to document the way that BIND4
worked ... which is the logical conclusion of some of the arguments that
are being made here.

Even ignoring any issues with doing incremental zone transfers, it is
important that a resolver be able to pick any of several different servers
for a zone, with confidence that it will receive the same answer (if it
receives an answer at all).  If the server selected also happens to be a
server for a child zone that would eventually need to be queried anyway,
that's fine, just avoids an extra query getting from parent to child.

But with incremental zone transfer it is essential that there is a well
defined version of what is the content of the zone, so that the clients
of those protocols can sanely apply updates - most particularly when the
server for the (incremental) transfer isn't one fixed system, but can
be any of several others.

That is, DNS database consistency is important, but (unless we were to ever
create some other method of ensuring it) it is the operators who have to 
make it happen - DNS software, at least using the DNS protocols as defined,
simply cannot, and more, must not, attempt to achieve this on the user's
behalf - doing so causes worse problems that not.

Tools to ensure that the parent domain has the correct glue, where glue
is needed, and to keep that correctly up to date when the child zone
makes changes would be a very worthwhile thing to create and make
available.    But they're not related to AXFR, which transfers one zone
from one server to another, and must do that without causing the zone
to change (perhaps as it is transferred along a chain of many servers).

kre






From owner-ietf@ietf.org  Sat Feb 15 06:14:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00678;
	Sat, 15 Feb 2003 06:14:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18k0G9-0004Ss-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 06:13:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18k0Fi-0004S8-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 06:13:02 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA00485
	for <ietf@ietf.org>; Sat, 15 Feb 2003 06:05:35 -0500 (EST)
Received: (qmail 67447 invoked by uid 1016); 15 Feb 2003 11:09:46 -0000
Date: 15 Feb 2003 11:09:46 -0000
Message-ID: <20030215110946.67446.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030215042944.95101.qmail@cr.yp.to> <200302150610.h1F6Akd6028212@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> Server 1 master for example.com and slave for division.example.com.
  [ and division.example.com decides to change its NS records: ]
> You receive email with the new delegation information. You update
> example.com

Your hypothetical scenario breaks down here, for two reasons:

   (1) That configuration violates RFC 1034.
   (2) My software doesn't allow that configuration.

Consequently, your claims of failure have no connection to reality. The
situation simply doesn't occur. (What actually happens is that the NS
record is updated when the child zone is transferred, as it should be.)

In more detail:

   (1) RFC 1034, sections 4.2.1 and 4.2.2, make crystal clear that the
       NS record for division.example.com is supposed to be exactly the
       same in the example.com zone and the division.example.com zone.

   (2) When my software is handling both zones, it enforces the RFC 1034
       requirement, by unifying the data for the two zones. There isn't
       a division.example.com NS record in the example.com zone separate
       from the same NS record in the division.example.com zone.

I realize that, in BIND, there are two independent disk files with the
two zones, so it's possible to separately change the NS record in the
division.com zone. But that violates RFC 1034, and my software simply
doesn't allow it.

You're going to have to learn that the protocol is not defined by BIND's
implementation decisions. If you persist in viewing everything through
the language of BIND's configuration files, you're going to keep making
false claims about the behavior of other DNS software. I strongly
recommend that you read the specifications of the standard DNS protocol,
specifically RFC 1034 and RFC 1035, before you comment further.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Sat Feb 15 07:47:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01883;
	Sat, 15 Feb 2003 07:47:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18k1fF-0005zd-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 07:43:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18k1ev-0005yk-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 07:43:09 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01768;
	Sat, 15 Feb 2003 07:35:41 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1FCdCd6028798;
	Sat, 15 Feb 2003 23:39:12 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302151239.h1FCdCd6028798@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "15 Feb 2003 11:09:46 -0000."
             <20030215110946.67446.qmail@cr.yp.to> 
Date: Sat, 15 Feb 2003 23:39:12 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Mark.Andrews@isc.org writes:
> > Server 1 master for example.com and slave for division.example.com.
>   [ and division.example.com decides to change its NS records: ]
> > You receive email with the new delegation information. You update
> > example.com
> 
> Your hypothetical scenario breaks down here, for two reasons:
> 
>    (1) That configuration violates RFC 1034.

	It does not.

>    (2) My software doesn't allow that configuration.

	Well as we keep pointing out your software is BROKEN.
 
> Consequently, your claims of failure have no connection to reality. The
> situation simply doesn't occur. (What actually happens is that the NS
> record is updated when the child zone is transferred, as it should be.)
> 
> In more detail:
> 
>    (1) RFC 1034, sections 4.2.1 and 4.2.2, make crystal clear that the
>        NS record for division.example.com is supposed to be exactly the
>        same in the example.com zone and the division.example.com zone.

	But the parent version *IS* a exact copy in both of the
	senarios given.  Just because it is not what is in the *old*
	copy of the child zone doesn't make it not a exact copy.

>    (2) When my software is handling both zones, it enforces the RFC 1034
>        requirement, by unifying the data for the two zones. There isn't
>        a division.example.com NS record in the example.com zone separate
>        from the same NS record in the division.example.com zone.

	Which is a problem in your software as it is a problem in BIND4
	and BIND 8.

> I realize that, in BIND, there are two independent disk files with the
> two zones, so it's possible to separately change the NS record in the
> division.com zone. But that violates RFC 1034, and my software simply
> doesn't allow it.
>
> implementation decisions. If you persist in viewing everything through
> the language of BIND's configuration files, you're going to keep making
> false claims about the behavior of other DNS software. I strongly
> recommend that you read the specifications of the standard DNS protocol,
> specifically RFC 1034 and RFC 1035, before you comment further.
>
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Sat Feb 15 12:44:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05350;
	Sat, 15 Feb 2003 12:44:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18k6Bt-00028X-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 12:33:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18k6Au-00027F-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 12:32:28 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05138
	for <IETF@ietf.org>; Sat, 15 Feb 2003 12:24:57 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA27492
	for <IETF@ietf.org>; Sat, 15 Feb 2003 09:28:27 -0800
Date: Sat, 15 Feb 2003 09:28:36 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <8991122056.20030215092836@brandenburg.com>
To: ietf <IETF@ietf.org>
Subject: Vienna IETF dates
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The web page shows the dates for Vienna as "July 13-18, 2003
(tentative)".

When will the dates be firm, so that folks can commit to travel
arrangements?

d/
--
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Sat Feb 15 16:36:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07625;
	Sat, 15 Feb 2003 16:36:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18k9x7-00076Z-00
	for ietf-list@ran.ietf.org; Sat, 15 Feb 2003 16:34:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18k9wn-00075e-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 16:34:09 -0500
Received: from cliffie.verisignlabs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07530;
	Sat, 15 Feb 2003 16:26:34 -0500 (EST)
Received: from thinkingcat.com (230.232.13.217.in-addr.dgcsystems.net [217.13.232.230])
  (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
  by cliffie.verisignlabs.com with esmtp; Sat, 15 Feb 2003 16:30:18 -0500
Message-ID: <3E4EB10B.7020408@thinkingcat.com>
Date: Sat, 15 Feb 2003 16:28:43 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
CC: iab@iab.org, iesg@ietf.org, ietf@ietf.org, rfc-editor@isi.edu
Subject: Re: Appeal against IESG decision
References: <13461.1041667648@munnari.OZ.AU>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Robert, all,

Here is the IAB's response to this appeal, as it is queued
to be announced on ietf-announce@ietf.org.

Regards,
Leslie.


================================================



On Saturday, January 4th 2003, Robert Elz filed an appeal with the
Internet Architecture Board (IAB).  The appeal concerned the IESG
decision to publish draft-ietf-ipngwg-addr-arch-v3-11.txt as a Draft
Standard and the subsequent IESG consideration of an appeal to the
IETF chair on this matter.


1. Background

The appeal asked the IAB to consider whether the Internet Engineering
Steering Group's (IESG's) decision to approve the publication of 
draft-ietf-ipngwg-addr-arch-v3-11.txt as a Draft Standard met the
process and technical standards of the IETF. The appeal contained the
following claims:

1) That the IESG failed to verify interoperability of 2
	independent implementations for the Internet Protocol
	version 6 (IPv6) unicast address format defined in the 
	above Internet-Draft.

2) That the IESG failed to verify that 2 independent implementations
	exist that prohibit the configuration of any IPv6 unicast
	address (not including those that start with binary 000)
	that does not have a 64-bit Interface-Identifier (Interface-ID).

3) That the document draft-ietf-ipngwg-addr-arch-v3-11.txt fails
	to clearly indicate (e.g. using customary MAY, SHOULD, MUST
	language) which parts of the document are mandatory or
	optional to implement or which parts of the document are
	interoperability requirements.

4) That the document uses the phrase "global scope" in a way that
	is materially confusing and causes a typical reader to
	incorrectly assume that "global scope" means "globally
	unique".

5) That the IESG has failed to verify that at least two interoperable
	implementations exist that prohibit the configuration of
	an interface-ID with the 'u' bit when the basis of the
	interface-ID is not a "globally unique token (MAC address
	or similar)".

6) That the document is materially unclear with respect to the
	language on when the 'u' bit of an Interface-ID is
	permitted to be set (or not set).

In its rejection of Robert Elz's original appeal to the IESG,
the IESG stated:

A) That there is no traditional requirement that implementation reports
	"include detailed verification that implementations enforce
	every statement...in the absence of explicit text requiring
	that an implementation make such checks."
	
B) That the requirement is that implementations operate when
	correctly configured, not that they interoperate when 
	incorrectly configured.
	
C) That there is no traditional requirement that an implementation
	disallow an operator from misconfiguring a protocol.
	
D) That the Internet-Draft in question does not require that
	the Interface-ID be globally unique when the 'u' bit
	is set; it merely requires that the Interface-ID comply
	with the EUI-64 specification when the 'u' bit is set.
	
E) That Elz's appeal is rejected by the IESG.


2. IAB Conclusion

Some of the issues raised in this appeal represent instances in which
the process or technical standards of the IETF were not met.  On that
basis, the IAB has determined that the IESG decision to advance this
specification on the IETF standards-track as a Draft Standard in its
current form, and the IESG's subsequent response to Elz's appeal, were
incorrect.

On that basis, the draft in its current form must not be published as a
IETF Draft Standard, and may be published as an IETF Proposed Standard.

The IAB response to this appeal is in three parts. The first part
contains particular facts determined by the IAB that relate to the
claims made in the appeal. The second part contains related
observations of the IAB arising from its review of documents germane to
the appeal. The third part contains recommendations to the IESG as to
possible actions on how to remedy the matters raised here.


2.1 Salient Facts

The IAB has determined the following facts regarding the Elz appeal:

I) An IP Address Architecture specification will always need to have
	some implementation requirements and interoperability 
	requirements.  Addressing and routing are inextricably
	linked.  Decisions about an address architecture necessarily
	have impacts on the forwarding of IP packets and on
	the routing protocols.  If there were no requirements
	in an IP Address Architecture, it is very unlikely that
	global interoperability could result in practice.  We
	further find that an IPv6 Address Architecture document
	belongs on the standards-track.
	
II) The IETF standards process does NOT require that a tested
	implementation prohibit misconfiguration of a protocol
	parameter, unless there is a specific written statement
	requiring such in the applicable specification document.

	    The IAB makes the additional comment that to interpret
	    the standards process requirements otherwise would be to
	    make it nearly impossible for any IETF standards-track
	    specification to advance and would be a new and undue
	    process burden on the IETF.

III) The IETF standards process does require that the default settings
	for each protocol parameter are valid and interoperable 
	when tested as part of an interoperability report.  It 
	is not required that each protocol parameter's default
	setting be individually documented in an interoperability 
	report.  The IETF requires interoperability testing, not
	conformance testing, as part of advancement beyond Proposed
	Standard according to RFC-2026.


2.2 IAB Considerations

In the course of reviewing the appeal and studying the facts 
germane to the appeal, the IAB also reached consensus on the 
following points:


IV) The Internet-Draft in question is not sufficiently clear 
	in specifying the implementation requirements and/or
	interoperability requirements for the IPv6 Address 
	Architecture.  
	
V) This lack of clarity on the part of the draft document violates
	criteria as specified in RFC-2026 and RFC-2119, by not
	containing clear documentation of the implementation
	requirements and interoperability requirements.  On this
	basis, the draft cannot be published in its current form on
	the IETF standards-track as a Draft Standard.	

VI) The questions of whether the IESG properly verified
	implementation report details regarding this I-D are moot,
	due to the consideration that the I-D itself was in violation
	of RFC-2026 and RFC-2119.

VII) The phrase 'global scope' does not mean 'globally unique'. There
	remains, however, some scope for confusion as to the precise
	meaning of the term 'global scope' for the average reader.
	
VIII) The existing specification of how the 'u' bit is used in
	an IPv6 unicast Interface-ID is clear, but the current
	version of the I-D under appeal is unclear regarding the
	implementation or interoperability requirements, if any, 
	that are related to the 'u' bit

IX) The IAB considers that the separation of the Interface-ID from
	the Subnet Identifier in IPv6 unicast addresses not starting 
	with binary 000 is a fundamental property of the IPv6 
	addressing and routing architecture and should be retained.

X) The IAB notes that RFC-2461 Section 4.6.2 permits an IPv6
	router to advertise an IPv6 unicast prefix-length of
	more than 64 bits while simultaneously setting the
	'autonomous configuration' flag to true.  Further,
	the RFC-2462 Section 5.5.3d does not explicitly require
	that the IPv6 prefix length not exceed 64 bits, as 
	the IPv6 Address Architecture draft requires.  Hence,
	we find a material conflict between the specifications
	in the IPv6 Address Architecture draft, in RFC-2461, and
	in RFC-2462.
	
XI) We believe that the conflicts noted in (X) occurred primarily 
	because of the failure of the I-D under appeal to comply 
	with the requirement for clearly specified implementation
	and interoperability requirements as per RFC-2119 and 
	RFC-2026.

XII) We concur with IESG statements paraphrased above as (A), (B),
	(C), and (D).  However, we reject the IESG conclusion (E) on
	the basis that the IESG's reply to Elz ignored the question
	of whether the current language regarding implementation
	requirements and interoperability requirements in draft-ietf-
	ipngwg-addr-arch-v3-11.txt is sufficiently clear and fully
	compliant with RFC-2026 and RFC-2119.


2.3 IAB Recommendations


The IAB makes the following recommendations with regard to draft-ietf-
ipngwg-addr-arch-v3-11.txt. An organizing theme behind these
recommendations is a desire on the part of the IAB to see the IPv6
addressing architecture stabilized as quickly as possible, with
interoperability requirements clearly specified, in an aid to
facilitating the more rapid implementation and deployment of IPv6 in the
Internet infrastructure.

As noted in Section 2, the IAB has determined that the draft in its
current form must not be published as an IETF Draft Standard.
	
a) We recommend to the IESG that the current version of the I-D draft
	be published as a Proposed Standard.

b) we recommend that the IESG consider the publication of subsequent
        updates to this document as per recommendations c) and d).

c) We recommend that, as an update to this document, and via a
        recommendation to the IESG, that the IPv6 Working
        Group create clear, specific, and concise implementation and
        interoperability requirements as per RFC-2026 and RFC-2119 in
        any revised version of the IPv6 Addressing Architecture
        document.  This includes, but is not limited to, the
        specification of any implementation or interoperability
        requirements relating to the use of the 'u' bit in an IPv6
        unicast Interface-ID.

d) We recommend that, as an update to this document, and via a
	recommendation to the IESG, that the IPv6 Working Group uses
	clearer specification language as per RFC-2026 and RFC-2119 to
	describe the requirement for a 64-bit Interface-ID in IPv6
	unicast addresses not starting with binary 000.
        
e) We recommend that, via a recommendation to the IESG, that the IPv6
        Working Group expeditiously revise RFC-2461 to:
	
	  - specifically note that it is not valid to configure an IPv6
	    router such that the 'autonomous configuration' bit is set
	    to TRUE AND the advertised IPv6 prefix length exceeds 64
	    bits AND the advertised IPv6 prefix does not start with
	    binary 000,
	
	and also expeditiously revise RFC-2462 to:
	
	  - specifically require that a host ignore a Prefix
	    Advertisement Option when the first three bits of the
	    advertised IPv6 prefix do not start with binary 000 AND the
	    advertised IPv6 prefix-length exceeds 64-bits.



Leslie Daigle,
for the IAB.

Robert Elz wrote:
> This is an appeal to the IAB against the IESG decision to reject
> my appeal against their earlier decision to approve the publication
> of draft-ietf-ipngwg-addr-arch-v3-11.txt as a Draft Standard.
> 
> The issues here are very simple, and no lengthy examination of mailing
> list archives, taking of evidence, hearing opinions, ... should be
> necessary in this case.   I believe that none of the facts are in any
> kind of dispute.
> 
> Those facts are
> 
> 1) RFC2026 says, in section 4.1.2 ...
> 
>    A specification from which at least two independent and interoperable
>    implementations from different code bases have been developed, and
>    for which sufficient successful operational experience has been
>    obtained, may be elevated to the "Draft Standard" level. [...]
> 
>    The requirement for at least two independent and interoperable
>    implementations applies to all of the options and features of the
>    specification.  In cases in which one or more options or features
>    have not been demonstrated in at least two interoperable
>    implementations, the specification may advance to the Draft Standard
>    level only if those options or features are removed.
> 
> 2) draft-ietf-ipngwg-addr-arch-v3-11.txt contains at least one (and perhaps
> two) features for which there are not two interoperable implementations.
> 
> The one is:
> 
> 	For all unicast addresses, except those that start with binary 
> 	value 000, Interface IDs are required to be 64 bits long and 
> 	to be constructed in Modified EUI-64 format.
> 
> There's no dispute that there are no interoperable implementations of
> this - there are no implementations of it at all (or no documented ones
> anyway).
> 
> Note that the spec actually gives no option here, other than the exceptions
> (the 000 addresses, and multicast), interface IDs are required to be 64
> bits long.    While all implementations I'm aware of allow 64 bit IDs,
> none have been presented that require it.  The draft *requires* it.
> 
> Any reasonable reading of 2026 would require that that feature of the
> specification be removed from the draft before the draft is permitted to
> be published as a draft standard.   Of course, as an alternative, the WG
> or IESG could have the draft, as it is, published as a Proposed Standard,
> and await the necessary two implementations of the feature before requesting
> advancement.
> 
> The IESG's opinion of this seems to be that the "two implementations of
> every feature" applies only where they consider it important enough to
> bother checking.   I have no problems with drafts advancing when no-one
> brings to the attention of the IESG that there is a problem in this area.
> But when a problem is pointed out, the clear words of 2026 really must be
> enforced.
> 
> The rationale for this requirement in 2026 is simple (as the IESG should
> know, as the author of 2026 is a member of the IESG).   First, it ensures
> that the text in the document is clear enough that it can be implemented
> in an interoperable way.   And second, it helps make sure that the
> document doesn't get cluttered with requirements in practice no-one
> bothers to implement - that is, that the document is a proper specification,
> and anyone reading the document can implement from it, with the
> expectation that their implementation will interoperate with others.
> 
> The quoted text from the draft fails both of those tests.   We have no
> implementations so we don't know that the text is clear enough to be
> implemented correctly.   It may seem obvious that the text is clear to
> any reader - but the IETF has always ignored "seem obvious" and required
> actual implementation experience as a demonstration.
> 
> Second, an implementation which did faithfully follow the words of the
> draft would fail to interoperate correctly with every other known
> implementation of it.   It may be claimed that it is the other
> implementations, or the way they are configured, that is at fault here,
> but that's not relevant - the aim is to get interoperability, and if
> we have operators configuring /112, /226, /227 and similar prefix
> lengths (that is, interface ID's that are 16, 2, or 1, and other,
> numbers of bits long) - and we do - then an implementation that enforced
> the 64 bit IID requirement (allowed only /64 prefix on an interface)
> would fail to interoperate with other implementations (with all other
> existing implementations).
> 
> This seems to be a "placeholder" fluff feature, being maintained to
> perhaps allow some future design to allow applications to simply "know"
> what is the prefix, and what is the interface-ID.   The requirement for
> existing implementations in 2026 is a specific requirement that such
> fluff be removed from docs before they're allowed to advance to DS status.
> 
> The extra requirement should be removed from the document, and then, if
> the WG so desires, published as a PS (or Experimental) RFC of its own.
> If it then becomes accepted and implemented, it could be merged back with
> the main document in a later revision.
> 
> 
> The second issue in the appeal to the IESG concerned the 'u' bit, which
> is one of the bits of the IID as defined.
> 
> The IESG referred to this as ...
> 
>  B/ Robert says "The requirement that where the 'u' bit (the inverted L 
>  bit from the MAC address) is set, the IID is globally unique."
> 
> and eventually concluded ...
> 
>  The IESG notes that there is no wording in
>  draft-ietf-ipngwg-addr-arch-v3-11.txt requiring that IIDs be globally
>  unique.
> 
> and then quoted two passages from the draft, only the last part of
> which is relevant.
> 
>    In
>    the resulting Modified EUI-64 format the "u" bit is set to one (1) to
>    indicate global scope, and it is set to zero (0) to indicate local
>    scope.
> 
> It is true that the doc does not expressly say "globally unique", what
> it says is "indicate global scope".
> 
> The draft also says ...
> 
>    Modified EUI-64 format based Interface identifiers may have global
>    scope when derived from a global token (e.g., IEEE 802 48-bit MAC or
>    IEEE EUI-64 identifiers [EUI64]) or may have local scope [...]
> 
> And ...
> 
>    The use of the universal/local bit in the Modified EUI-64 format
>    identifier is to allow development of future technology that can take
>    advantage of interface identifiers with global scope.
> 
> I doubt I'm the only reader to come to the conclusion that "have global
> scope" actually means "be globally unique".   What's more, a review of
> various IPv6 related mailing lists will show this opinion expressed over
> and over again.   Clearly there are many readers who have leapt to this
> wrong conclusion, if it is in fact wrong, and as the IESG have concluded,
> there is no actual expectation that the IID will be any more than probably
> globally unique, then the draft should probably be more explicit in saying
> that, rather than allowing readers to leap to the incorrect interpretation.
> 
> But there is more to this than the IESG apparently understood.   The question
> isn't just whether the 'u' bit being set implies that the IID is globally
> unique (or has "global scope") but whether there are any implementations at
> all that actually enforce the setting of the 'u' bit only when the IID
> has been formed from a (probably) globally unique token (a MAC address
> or similar).   Here there has been one implementation reported on the
> mailing list (but not in the interoperability report) - but for DS status,
> one implementation isn't enough.
> 
> Other implementations allow the user to configure the 'u' bit set without
> having any knowledge or expectation, or reason to assume, that the address
> is derived from any kind of globally unique token (or token with global scope).
> What's more, they do this for good reason, as without that ability, users have
> no way to remove a NIC, and replace it with another, and retain the original
> (auto-configured) IPv6 address (which being based upon the MAC address that
> the old NIC provided, would have had the 'u' bit set).   In this case the
> address is in fact based upon a globally unique token, but the implementation
> has no way to know that, and so must also allow the 'u' bit to be set when
> the rest of the IID is 0, or 1, or 2, which are most certainly not tokens
> with any kind of global scope.    What's more, as the old NIC may be now in
> use in some other host, there's no reason in the example cited to assume that
> there's any uniqueness at all - for correct IPv6 operation, the NIC can't
> be connected to the same subnet as where it used to be, but beyond that
> IPv6 works just fine with the same IID on different nets).
> 
> Once again, we have a feature of the specification which is either not
> implemented, or at best, is not clear.
> 
> The IESG's response to all of this is ...
> 
>  When considering this appeal, it is clear from the interoperability
>  reports that there are implementations that generate the interface ID
>  from the EUI-64 identifier, which makes it be 64 bits long. It is
>  also clear that the uniqueness properties of EUI-64 based identifiers
>  will be the same as the EUI-64 identifiers from which they are derived
>  (which is slightly weaker than a requirement for global uniqueness).
> 
> Yes - though in practice implementations (bar one) allow addresses to be
> generated from EUI-64's, but they also allow indistinguishable addresses
> to be manually configured - so in practice (which is what the interoperable
> implementation requirement is attempting to ensure that the specification
> conforms to) extracting an IID from an IPv6 address, and expecting it to
> have any kind of similar properties of global uniqueness as an EUI-64
> would be a false expectation, and the draft should not lead people into
> expecting otherwise.   Only if implementations actually enforced this
> requirement (which they can easily do, as the one which has done it shows,
> though of course, this loses functionality) would this expectation be
> justified.
> 
>  So for at least some implementations, they are capable of acting as
>  specified in the document being challenged.
> 
> No.   The requirement challenged is a "must only be" - or if you like,
> a MUST NOT.   The fact that it is possible to conform with the spec
> using existing implementations has nothing to do with the issue at all.
> 
> The IESG's response here would be the equivalent of responding to a
> requirement that "All cars must be red" by pointing to a few red cars
> and saying "see, it can be done".   That it can be done isn't the issue,
> the issue is that the specification says it MUST be done.   To be advanced
> to DS, all that is required is that there be 2 conforming implementations,
> what the rest do is irrelevant (until the doc is ready to be advanced to full
> standard).   For some specifications, 2 implementations itself is a large
> hurdle, for IPv6, it isn't, there are many implementations.   That none
> of them have implemented one of the requirements of the doc, and only one
> another, should be a pretty obvious red flag that these requirements should
> not remain in the document.
> 
> The IESG also says ...
> 
>  We traditionally require that things interoperate when configured 
>  correctly, not that they interoperate when configured incorrectly, or 
>  that it be impossible to configure them incorrectly.
> 
> Of course, that's as it should be.   That is, except where the specification
> explicitly says that something must not be possible.   There's no point
> keeping a prohibition in the specification if no-one takes any notice of
> it.   There's no difference here to keeping some other feature that no-one
> bothers to implement.
> 
> And again from the IESG ...
> 
>  Implementation reports are used to verify that independent 
>  implementations can succesfully interoperate. This is a quality check 
>  on the clarity of the documents.
> 
> Yes.   But the IESG have managed to conveniently forget the other purpose
> for the requirement - that is, as a check that the features are actually
> being implemented, and that the document isn't describing things which in
> practice everyone ignores.
> 
> But even without that, here we have no quality check on the clarity of
> the relevant statements in the documents - no-one has implemented them.
> (No-one has implemented one, there's only one implementation of the other).
> We're only guessing if we assume that the statements are clear enough.
> 
> IESG again:
> 
>  Requiring explicit verification on all statements would be a change to 
>  existing practice and one that would likely increase the difficulty in 
>  advancing documents on the standards track.
> 
> That's what was intended.   If existing practice has been to ignore
> the two implementation requirement, when it is known not to be met,
> then I submit that the IESG has been operating contrary to the clear
> instructions of 2026.
> 
> It need not be onerous to enforce this however - it is entirely reasonable
> to expect the community to point out any flaws in the implementation
> reports as published.   If there are no reported problems, the IESG,
> and the community, are justified in assuming that the reports fully
> document the required interoperability of every feature.   Where there
> are reports that interoperability of some feature has not been properly
> documented, then it should be easy for the implementation report to be
> corrected, if the feature has in fact been implemented and tested.  If it
> has been implemented, but not tested, then the report should be seen as
> being of benefit, in showing a potential trouble area, not as a burden.
> If testing shows that all works, then there's real harm done, and the
> implementation report can be corrected.   If testing shows 
> non-interoperability, then clearly there's something that needs fixing
> (in some cases, just implementation bugs, after which further testing
> will show the specification is fine).   On the other hand if testing is
> not possible, because the feature has not been implemented, then it really
> should be removed from the document before it is advanced.   That's what
> the requirement in 2026 is there for.
> 
> The IESG again ...
> 
>  There are many places in IETF standards where a field is stated to be
>  a specific length or a value to be within a range. Requiring that the
>  limits be enforced in software for all of these cases would put a
>  significant extra burden on the implementers and the documenters of
>  the implementations for questionable benefit.
> 
> This is once again based upon a misunderstanding of what is required.
> No-one is requiring that the limits be enforced in general.   What is
> being asked is that someone (sometwo really) has done it.   What's the
> point of a requirement that is universally ignored?   There is none,
> it is misleading, and should not be permitted in a Draft Standard.
> 
> I would ask that the IAB instruct the IESG to overturn their decision
> to publish the draft (draft-ietf-ipngwg-addr-arch-v3-11.txt) as a
> Draft Standard, and at their choice, either publish it as a Proposed
> Standard, or return it to the working group for amendments that will
> allow it to be published as a Draft Standard.
> 
> kre
> 
> ps: I would also request that the RFC editor continue to defer
> publication of this draft until the IAB has dealt with this appeal.
> 


-- 

-------------------------------------------------------------------
"An essential element of a successful journey
    is recognizing when you have arrived."
   -- ThinkingCat  (c.1983 - 2002)

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------




From owner-ietf@ietf.org  Mon Feb 17 09:13:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22612;
	Mon, 17 Feb 2003 09:13:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18kli4-0001ZH-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 08:53:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18klhS-0001Yy-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 08:52:50 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22150;
	Mon, 17 Feb 2003 08:44:52 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18kldC-0003L1-00; Mon, 17 Feb 2003 13:48:26 +0000
Date: Mon, 17 Feb 2003 13:48:23 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Mark.Andrews@isc.org
cc: "D. J. Bernstein" <djb@cr.yp.to>, "" <ietf@ietf.org>, "" <iesg@ietf.org>,
        "" <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <200302151239.h1FCdCd6028798@drugs.dv.isc.org>
Message-ID: <Pine.GSO.4.50.0302171251240.3134-100000@artemis.ee.surrey.ac.uk>
References: <200302151239.h1FCdCd6028798@drugs.dv.isc.org>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.5 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,REFERENCES,
	      SPAM_PHRASE_00_01,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18kldC-0003L1-00*8cw17LwAtKQ* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 15 Feb 2003 Mark.Andrews@isc.org wrote:

> >    (2) My software doesn't allow that configuration.
>
> 	Well as we keep pointing out your software is BROKEN.

Saying it's broken implies the act of breakage.

At what point was the software NOT broken?

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Mon Feb 17 10:31:33 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23962;
	Mon, 17 Feb 2003 10:31:33 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18knDw-0002cp-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 10:30:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18knCE-0002cE-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 10:28:42 -0500
Received: from mail.wrs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23696;
	Mon, 17 Feb 2003 10:20:44 -0500 (EST)
Received: from IDLEWYLDE.windriver.com ([147.11.233.30])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id HAA07984;
	Mon, 17 Feb 2003 07:23:17 -0800 (PST)
Message-Id: <5.1.0.14.2.20030217100313.03682e70@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 17 Feb 2003 10:13:52 -0500
To: ops-area@ietf.org, ops-nm@ietf.org, ietf@ietf.org, nmrg@ibr.cs.tu-bs.de
From: Margaret Wasserman <mrw@windriver.com>
Subject: XMLCONF Proposal
Cc: xmlconf@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk


Hi All,

We have a proposal available for a new configuration protocol
that may be of interest to folks on these lists.  The proposal
has been published an an I-D, and can be found at:

http://www.ietf.org/internet-drafts/draft-enns-xmlconf-spec-00.txt

We believe that this proposal addresses many of the operator
and vendor requirements for a configuration protocol that have
been gathered and analyzed over the past couple of years.

We will be requesting a BOF to discuss this proposal in San
Francisco, but before a BOF can be scheduled, we will need to
demonstrate sufficient community interest in this proposal.

So, if you believe that this proposal warrants further work
within the IETF, please send your feedback ASAP to
xmlconf@ops.ietf.org.

Please DO NOT cross-post replies to all of the groups cc:ed
on this message.

Thanks,
Margaret





From owner-ietf@ietf.org  Mon Feb 17 15:22:57 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00383;
	Mon, 17 Feb 2003 15:22:57 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18krlY-00075a-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 15:21:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18krlM-000758-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 15:21:16 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA00159;
	Mon, 17 Feb 2003 15:13:11 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1HKG4d6046986;
	Tue, 18 Feb 2003 07:16:08 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302172016.h1HKG4d6046986@drugs.dv.isc.org>
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
Cc: Mark_Andrews@isc.org, "D. J. Bernstein" <djb@cr.yp.to>, "" <ietf@ietf.org>,
        "" <iesg@ietf.org>, "" <namedroppers@ops.ietf.org>
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "Mon, 17 Feb 2003 13:48:23 -0000."
             <Pine.GSO.4.50.0302171251240.3134-100000@artemis.ee.surrey.ac.uk> 
Date: Tue, 18 Feb 2003 07:16:04 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Sat, 15 Feb 2003 Mark.Andrews@isc.org wrote:
> 
> > >    (2) My software doesn't allow that configuration.
> >
> > 	Well as we keep pointing out your software is BROKEN.
> 
> Saying it's broken implies the act of breakage.
> 
> At what point was the software NOT broken?

	In the original design specs.  RFC 1034 and RFC 1035.  If
	they had been followed then we wouldn't be havin this
	discussion.
 
	Mark
> L.
> 
> <http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Mon Feb 17 15:40:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00908;
	Mon, 17 Feb 2003 15:40:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ks5s-0007nr-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 15:42:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ks4L-0007nI-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 15:40:53 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00741;
	Mon, 17 Feb 2003 15:32:51 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18ks06-0005F7-00; Mon, 17 Feb 2003 20:36:30 +0000
Date: Mon, 17 Feb 2003 20:36:29 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Mark.Andrews@isc.org
cc: Mark_Andrews@isc.org, "D. J. Bernstein" <djb@cr.yp.to>, "" <ietf@ietf.org>,
        "" <iesg@ietf.org>, "" <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <200302172016.h1HKG4d6046986@drugs.dv.isc.org>
Message-ID: <Pine.GSO.4.50.0302172031540.3860-100000@artemis.ee.surrey.ac.uk>
References: <200302172016.h1HKG4d6046986@drugs.dv.isc.org>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.5 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,REFERENCES,
	      SPAM_PHRASE_00_01,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18ks06-0005F7-00*gIdMMb.mkO2* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Tue, 18 Feb 2003 Mark.Andrews@isc.org wrote:

> > On Sat, 15 Feb 2003 Mark.Andrews@isc.org wrote:
> >
> > > >    (2) My software doesn't allow that configuration.
> > >
> > > 	Well as we keep pointing out your software is BROKEN.
> >
> > Saying it's broken implies the act of breakage.
> >
> > At what point was the software NOT broken?
>
> 	In the original design specs.  RFC 1034 and RFC 1035.  If
> 	they had been followed then we wouldn't be havin this
> 	discussion.

original design specs != "your software".

Are you claiming that djb's djbdns software was incorrectly
implemented? Please be clear, for Dan "we're all suffering because of
a few inconsiderate people" Bernstein's benefit -- and ultimately our
benefit, too.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Mon Feb 17 21:34:29 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06736;
	Mon, 17 Feb 2003 21:34:29 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18kxYa-0001Zy-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 21:32:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18kxY9-0001Zi-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 21:32:01 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA06486;
	Mon, 17 Feb 2003 21:23:52 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1I2RSd6053173;
	Tue, 18 Feb 2003 13:27:29 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302180227.h1I2RSd6053173@drugs.dv.isc.org>
To: mw-list-namedroppers@csi.hu
Cc: Name Droppers <namedroppers@ops.ietf.org>
cc: ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "Mon, 17 Feb 2003 14:28:33 MDT."
             <20030217202833.GA16887@thales.memphis.edu> 
Date: Tue, 18 Feb 2003 13:27:28 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Sat, Feb 15, 2003 at 05:10:46PM +1100, Mark.Andrews@isc.org wrote:
> > 	Your software (and BIND 8) causes operational problems by not
> > 	preserving zone contents.
> [...]
> > 	Senario 1.
> 
> In order to understand your claim about the operational problems while
> using djbdns, could you tell us how Scenario 1 is accomplished with
> tinydns/axfrdns? Could you give us a URL pointing at a webpage that
> contains the output of your experiments?
> 
> > 	You update example.com adjusting
> > 	its serial.  
> 
> In particular, could you tell us what is the relevance of the serial
> number to tinydns's update procedures?
> 
> 
> > 	Senario 2.
> 
> [...]
> 
> > 	This is a common implemention error caused by trying to
> > 	stuff all zones into a common database.  BIND 4 got it
> > 	wrong.  BIND 8 got it wrong.
> > 
> > 	You want us all to keep repeating this mistake.
> 
> But I thought djbdns did _not_ get it wrong.  Or if you think it did,
> could you show us the experiment that verifies the claim, that is, it
> accomplishes Scenario 2 with tinydns/axfrdns servers?
> 
> Mate
> 
> Mate Wierdl | Dept. of Math. Sciences | University of Memphis  
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>

	It's easy enough to demonstate.  The master server is 10.53.0.2.
	10.53.0.1 is dbj's software.   I used the FreeBSD port system to
	install it.

djbdns-1.05_2       A collection of secure and reliable DNS tools

tcpclient 10.53.0.2 53 axfr-get child.example.net zone.child.example.net zone.child.example.net.tmp
tcpclient 10.53.0.2 53 axfr-get example.net zone.example.net zone.example.net.tmp
sort -u zone.* > data
make

	You will note that it actually *merges* the records.
	ns2.child.example.net doesn't exist due to a typo in
	child.example.net.  I was taking Dan's word that it
	took the child data.

	Merges are just as bad as taking data just from the child
	zone.  In both cases slaves off 10.53.0.1 will be left with
	data that was not in the original master files.

	I presume for a real world server that you would need to
	call tcpclient periodically and remake data if the zone
	files have changed.   It looks like they axfr-get is
	designed to be called independently of the database make.

	I suspect no-one would run tinydns in the senarios described.
	It's designed for a collection of servers that all serve a
	identical set of zones from a single master.  Trying to use
	it in any other configuration is just cumbersome.  There
	really is no incoming zone maintanence.  You have to roll
	your own from what I can see.  axfr-get will check the
	serial but that is far short of full zone maintenance.
	axfr-get get need to be called with the right periodicity.

	Mark

; <<>> DiG 9.3.0s20021115 <<>> axfr child.example.net @10.53.0.2
;; global options:  printcmd
child.example.net.	10	IN	SOA	. . 1 3600 1200 360000 10
child.example.net.	10	IN	NS	ns1.child.example.net.
child.example.net.	10	IN	NS	ns2.child.example.net.
ns1.child.example.net.	10	IN	A	10.53.0.1
ns1.child.example.net.	10	IN	A	10.53.0.2
child.example.net.	10	IN	SOA	. . 1 3600 1200 360000 10
;; Query time: 43 msec
;; SERVER: 10.53.0.2#53(10.53.0.2)
;; WHEN: Tue Feb 18 11:50:46 2003
;; XFR size: 7 records (messages 1)


; <<>> DiG 9.3.0s20021115 <<>> axfr child.example.net @10.53.0.1
;; global options:  printcmd
child.example.net.	10	IN	SOA	. . 1 3600 1200 360000 10
child.example.net.	10	IN	NS	ns1.child.example.net.
child.example.net.	10	IN	NS	ns2.child.example.net.
ns1.child.example.net.	10	IN	A	10.53.0.1
ns1.child.example.net.	10	IN	A	10.53.0.2
ns2.child.example.net.	10	IN	A	10.53.0.2
child.example.net.	10	IN	SOA	. . 1 3600 1200 360000 10
;; Query time: 5 msec
;; SERVER: 10.53.0.1#53(10.53.0.1)
;; WHEN: Tue Feb 18 11:51:02 2003
;; XFR size: 8 records (messages 7)

; <<>> DiG 9.3.0s20021115 <<>> axfr example.net @10.53.0.2
;; global options:  printcmd
example.net.		10	IN	SOA	. . 1 3600 1200 360000 10
example.net.		10	IN	NS	ns1.example.net.
example.net.		10	IN	NS	ns2.example.net.
child.example.net.	10	IN	NS	ns1.child.example.net.
child.example.net.	10	IN	NS	ns2.child.example.net.
ns1.child.example.net.	10	IN	A	10.53.0.1
ns2.child.example.net.	10	IN	A	10.53.0.2
ns1.example.net.	10	IN	A	10.53.0.1
ns2.example.net.	10	IN	A	10.53.0.2
example.net.		10	IN	SOA	. . 1 3600 1200 360000 10
;; Query time: 3 msec
;; SERVER: 10.53.0.2#53(10.53.0.2)
;; WHEN: Tue Feb 18 11:52:04 2003
;; XFR size: 11 records (messages 1)


; <<>> DiG 9.3.0s20021115 <<>> axfr example.net @10.53.0.1
;; global options:  printcmd
example.net.		10	IN	SOA	. . 1 3600 1200 360000 10
child.example.net.	10	IN	NS	ns1.child.example.net.
child.example.net.	10	IN	NS	ns2.child.example.net.
example.net.		10	IN	NS	ns1.example.net.
example.net.		10	IN	NS	ns2.example.net.
ns1.child.example.net.	10	IN	A	10.53.0.1
ns1.child.example.net.	10	IN	A	10.53.0.2
ns1.example.net.	10	IN	A	10.53.0.1
ns2.child.example.net.	10	IN	A	10.53.0.2
ns2.example.net.	10	IN	A	10.53.0.2
example.net.		10	IN	SOA	. . 1 3600 1200 360000 10
;; Query time: 5 msec
;; SERVER: 10.53.0.1#53(10.53.0.1)
;; WHEN: Tue Feb 18 11:51:30 2003
;; XFR size: 12 records (messages 11)

; <<>> DiG 9.3.0s20021115 <<>> ns child.example.net @10.53.0.1
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56624
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;child.example.net.		IN	NS

;; ANSWER SECTION:
child.example.net.	10	IN	NS	ns1.child.example.net.
child.example.net.	10	IN	NS	ns2.child.example.net.

;; ADDITIONAL SECTION:
ns1.child.example.net.	10	IN	A	10.53.0.1
ns1.child.example.net.	10	IN	A	10.53.0.2
ns2.child.example.net.	10	IN	A	10.53.0.2

;; Query time: 1 msec
;; SERVER: 10.53.0.1#53(10.53.0.1)
;; WHEN: Tue Feb 18 12:11:45 2003
;; MSG SIZE  rcvd: 119


; <<>> DiG 9.3.0s20021115 <<>> ns child.example.net @10.53.0.2
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12751
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;child.example.net.		IN	NS

;; ANSWER SECTION:
child.example.net.	10	IN	NS	ns2.child.example.net.
child.example.net.	10	IN	NS	ns1.child.example.net.

;; ADDITIONAL SECTION:
ns1.child.example.net.	10	IN	A	10.53.0.1
ns1.child.example.net.	10	IN	A	10.53.0.2

;; Query time: 1 msec
;; SERVER: 10.53.0.2#53(10.53.0.2)
;; WHEN: Tue Feb 18 12:12:02 2003
;; MSG SIZE  rcvd: 103


--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Mon Feb 17 23:28:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08634;
	Mon, 17 Feb 2003 23:28:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18kzMq-0006gF-00
	for ietf-list@ran.ietf.org; Mon, 17 Feb 2003 23:28:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18kzMi-0006fx-00
	for ietf@ran.ietf.org; Mon, 17 Feb 2003 23:28:20 -0500
Received: from TYO201.gate.nec.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08510
	for <ietf@ietf.org>; Mon, 17 Feb 2003 23:20:13 -0500 (EST)
Received: from mailgate4.nec.co.jp ([10.7.69.193])
	by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id h1I4Nww20055
	for <ietf@ietf.org>; Tue, 18 Feb 2003 13:23:58 +0900 (JST)
Received: from mailsv.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP
	id h1I4Nv308298 for <ietf@ietf.org>; Tue, 18 Feb 2003 13:23:57 +0900 (JST)
Received: from kaishu.jp.nec.com (kaishu.jp.nec.com [10.26.220.5]) by mailsv.nec.co.jp (8.11.6/3.7W-MAILSV-NEC) with ESMTP
	id h1I4L1q10264 for <ietf@ietf.org>; Tue, 18 Feb 2003 13:23:22 +0900 (JST)
Received: from [10.56.88.192] by mail.jp.nec.com; Tue, 18 Feb 2003 13:21:01 +0900
To: ietf@ietf.org
Reply-To: m-shimada@ab.jp.nec.com
Subject: Protocl Status
Message-Id: <20030218132207m-shimada@mail.jp.nec.com>
Mime-Version: 1.0
X-Mailer: WeMail32[2.01] ID:Unregistered
From: "=?ISO-2022-JP?B?GyRCRWhFRD47QDgbKEI=?=	" <m-shimada@ab.jp.nec.com>
Date: Tue, 18 Feb 2003 13:22:07 +0900
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a following question. Please someone teach me.

RFC2400(INTERNET OFFICIAL PROTOCOL STANDARDS) describes a 
status like Req or Rec for each Protocol but RFC2500 does NOT 
describe status. RFC2500 obsoletes RFC2400.
What RFC describes a status for each protocol?
Where can I find status description for each protocol? 

Thanks,
Masao


part of RFC2400 is as follows
--------------------------------------------------------------------
Internet Architecture Board Standards Track                [Page 20]

RFC 2400                   Internet Standards         September 1998


6.2.  Standard Protocols

Protocol   Name                                  Status    RFC STD *
========   ===================================== ======== ==== === =
--------   Internet Official Protocol Standards  Req      2400   1
--------   Assigned Numbers                      Req      1700   2
--------   Host Requirements - Communications    Req      1122   3
--------   Host Requirements - Applications      Req      1123   3
IP         Internet Protocol                     Req       791   5
            as amended by:--------
--------     IP Subnet Extension                 Req       950   5
--------     IP Broadcast Datagrams              Req       919   5
--------     IP Broadcast Datagrams with Subnets Req       922   5
ICMP       Internet Control Message Protocol     Req       792   5
IGMP       Internet Group Multicast Protocol     Rec      1112   5
UDP        User Datagram Protocol                Rec       768   6
TCP        Transmission Control Protocol         Rec       793   7
TELNET     Telnet Protocol                       Rec   854,855   8
FTP        File Transfer Protocol                Rec       959   9
SMTP       Simple Mail Transfer Protocol         Rec       821  10



From owner-ietf@ietf.org  Tue Feb 18 04:25:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23171;
	Tue, 18 Feb 2003 04:25:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18l3zI-0000Zt-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 04:24:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18l3yZ-0000Za-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 04:23:43 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22946;
	Tue, 18 Feb 2003 04:15:30 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2E25262581; Tue, 18 Feb 2003 10:19:19 +0100 (CET)
Date: Tue, 18 Feb 2003 10:19:19 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>, Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: A formality.... (Re: axfr-clarify's fraudulent claims of consensus)
Message-ID: <332070000.1045559959@askvoll.hjemme.alvestrand.no>
In-Reply-To: <Pine.LNX.4.44.0302141750260.3790-100000@commander.av8.net>
References:  <Pine.LNX.4.44.0302141750260.3790-100000@commander.av8.net>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On fredag, februar 14, 2003 17:57:45 -0500 Dean Anderson <dean@av8.com> 
wrote:

> As you note, they didn't conform to a BCP. There is no requirement (or
> implication even) that one should conform to a Best Common Practice.
> These serve to distribute helpful advice to the community and document
> practices that have worked for others, in situations that may be
> different.
>
> The AXFR issue is compliance with a required standard, and its definition.
> Much more serious concerns and issues are at stake.

Note: The IETF has never made *any* standard that the IETF required people 
to conform to, unless they wanted to truthfully claim conformance to that 
standard.
At one point in time it made sense to say that "to be an Internet device, 
you have to conform to this set of standards"; currently, the ways in which 
IETF standards depend on each other are complex enough that this doesn't 
make much sense any more.

As a result, the distinction between "Elective", "Recommended" and 
"Required" protocols has largely fallen into disuse; RFC 2400 was the last 
version of the Official Protocol Standards document that even bothered to 
list them - the current version is RFC 3300.

At the time of RFC 2400, the set of Required standards were:

--------   Internet Official Protocol Standards      Req      2400   1
--------   Assigned Numbers                          Req      1700   2
--------   Host Requirements - Communications        Req      1122   3
--------   Host Requirements - Applications          Req      1123   3
IP         Internet Protocol                         Req       791   5
--------     IP Subnet Extension                     Req       950   5
--------     IP Broadcast Datagrams                  Req       919   5
--------     IP Broadcast Datagrams with Subnets     Req       922   5
ICMP       Internet Control Message Protocol         Req       792   5

Here is the status of the DNS standards in that document:

DOMAIN     Domain Name System                        Rec 1034,1035  13
DNS-MX     Mail Routing and the Domain System        Rec       974  14

axfr-clarify will have to enter the process as a Proposed Standard.
Both Proposed Standards and BCPs are encouraging people to do things a 
certain way; if anything, I consider a BCP slightly more forceful.

                  Harald Alvestrand





From owner-ietf@ietf.org  Tue Feb 18 07:28:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26348;
	Tue, 18 Feb 2003 07:28:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18l6oS-0004iC-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 07:25:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18l6nt-0004hp-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 07:24:53 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26100
	for <IETF@ietf.org>; Tue, 18 Feb 2003 07:16:41 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 98BB662586; Tue, 18 Feb 2003 13:20:28 +0100 (CET)
Date: Tue, 18 Feb 2003 13:20:28 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dave Crocker <dhc2@dcrocker.net>, ietf <IETF@ietf.org>
Subject: Re: Vienna IETF dates
Message-ID: <6640000.1045570828@askvoll.hjemme.alvestrand.no>
In-Reply-To: <8991122056.20030215092836@brandenburg.com>
References:  <8991122056.20030215092836@brandenburg.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA26348

The dates have been fixed for some time; the contract was (finally!) signed 
last week, so the last vestiges of doubt should have disappeared now.

That said, the delay in getting the contract done was NOT something I find 
acceptable, and we'll certainly work on getting this done a GOOD bit 
earlier in the future.

November is already signed.

             Harald



--On lørdag, februar 15, 2003 09:28:36 -0800 Dave Crocker 
<dhc2@dcrocker.net> wrote:

> The web page shows the dates for Vienna as "July 13-18, 2003
> (tentative)".
>
> When will the dates be firm, so that folks can commit to travel
> arrangements?
>
> d/
> --
>  Dave <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  t +1.408.246.8253; f +1.408.850.1850
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, which
> is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on
> what to pass are made solely by Raffaele D'Albenzio.
>





From owner-ietf@ietf.org  Tue Feb 18 08:35:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27867;
	Tue, 18 Feb 2003 08:35:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18l7uC-0005gd-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 08:35:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18l7u0-0005gF-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 08:35:16 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27762;
	Tue, 18 Feb 2003 08:27:03 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 8D4A262586; Tue, 18 Feb 2003 14:30:51 +0100 (CET)
Date: Tue, 18 Feb 2003 14:30:51 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call:
 CR-LDP Extensions for ASON to Informational ] 
Message-ID: <31100000.1045575051@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20899.1044967504@munnari.OZ.AU>
References: <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu> 
 <20899.1044967504@munnari.OZ.AU>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On tirsdag, februar 11, 2003 19:45:04 +0700 Robert Elz 
<kre@munnari.OZ.AU> wrote:

> IETF Consensus is the IETF's way of agreeing to some action.   The IETF
> makes that decision, the IESG (currently anyway) is tasked with
> determining whether or not the IETF has actually made a decision.   IETF
> Consensus clearly requires a last call be made.   It does not (of itself)
> require publication of anything at all - publication may be made to
> record the consensus, it does not cause it, and is not required to obtain
> it.

Given that a large portion of the IETF does not in fact subscribe to the 
ietf-announce list, and that in some cases the IETF consensus is pretty 
obvious (for instance when the decision is just paperwork following up on 
another IETF consensus decision), I wouldn't even say that a Last Call is 
always required.

But it's certainly one tool, and a fairly powerful one, for getting 
objections out in public.

(now, does the recent DJB discussion of axfr-clarify by itself invalidate 
WG or IETF consensus? I think not.... but it's certainly input that has to 
be considered when determining the IETF consensus.)



From owner-ietf@ietf.org  Tue Feb 18 13:26:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03963;
	Tue, 18 Feb 2003 13:26:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lCEG-0000B9-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 13:12:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lCDj-0000AM-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 13:11:55 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03342
	for <IETF@ietf.org>; Tue, 18 Feb 2003 13:03:40 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA06777;
	Tue, 18 Feb 2003 10:07:10 -0800
Date: Tue, 18 Feb 2003 09:52:24 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <66161472274.20030218095224@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: ietf <IETF@ietf.org>
Subject: Re: Vienna IETF dates
In-Reply-To: <6640000.1045570828@askvoll.hjemme.alvestrand.no>
References: <8991122056.20030215092836@brandenburg.com>
 <6640000.1045570828@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harald,

Tuesday, February 18, 2003, 4:20:28 AM, you wrote:
HTA> The dates have been fixed for some time; the contract was (finally!) signed
HTA> last week, so the last vestiges of doubt should have disappeared now.

excellent.  thanks.

d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Tue Feb 18 13:36:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04179;
	Tue, 18 Feb 2003 13:36:50 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lCdQ-0000mc-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 13:38:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lCcx-0000m1-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 13:37:59 -0500
Received: from turing-police.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04033;
	Tue, 18 Feb 2003 13:29:44 -0500 (EST)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu (localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.12.8.Alpha0/8.12.8.Alpha0) with ESMTP id h1IIWbhC016614;
	Tue, 18 Feb 2003 13:32:37 -0500
Message-Id: <200302181832.h1IIWbhC016614@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6 02/09/2003 with nmh-1.0.4+dev
To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: Your message of "Mon, 17 Feb 2003 13:48:23 GMT."
             <Pine.GSO.4.50.0302171251240.3134-100000@artemis.ee.surrey.ac.uk> 
References: <200302151239.h1FCdCd6028798@drugs.dv.isc.org>
            <Pine.GSO.4.50.0302171251240.3134-100000@artemis.ee.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-396084903P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Feb 2003 13:32:27 -0500
Sender: owner-ietf@ietf.org
Precedence: bulk

--==_Exmh_-396084903P
Content-Type: text/plain; charset=us-ascii

On Mon, 17 Feb 2003 13:48:23 GMT, Lloyd Wood said:

> Saying it's broken implies the act of breakage.
> 
> At what point was the software NOT broken?

It's quite conceivable the software was BAD (Broken As Designed).

It's pretty clear to me that either djbdns or BIND was BAD. I'm just not
sure which.. :)

http://www.catb.org/~esr/jargon/html/entry/BAD.html

--==_Exmh_-396084903P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE+Unw7cC3lWbTT17ARAj8mAJ9Sh1pxAnTf6/+Zm6PU6ZZKZ8kHTwCdGUfv
BP2xGbkQywKOaPw0rNODwPY=
=tDGn
-----END PGP SIGNATURE-----

--==_Exmh_-396084903P--



From owner-ietf@ietf.org  Tue Feb 18 20:01:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13450;
	Tue, 18 Feb 2003 20:01:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lIb7-0000Ur-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 20:00:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lIar-0000U8-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 20:00:13 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13115;
	Tue, 18 Feb 2003 19:51:46 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1J0sU4U003065;
	Wed, 19 Feb 2003 11:54:32 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302190054.h1J0sU4U003065@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Tue, 18 Feb 2003 18:46:19 CDT."
             <Pine.LNX.4.44.0302181821280.1529-100000@commander.av8.net> 
Date: Wed, 19 Feb 2003 11:54:30 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Good. You found a bug in an implementation. I thought such things were
> off-topic for this list.  This bug doesn't mean that AXFR is broken.
> Bind 8 did not have this bug, yet it has the common understanding of AXFR.
> 
> Let me summarize the discussion:
> 
> Everyone agrees that AXFR specification in RFC 1034 is ambiguous.
> 
> Some people, many associated with Bind 9 development, assert that it is
> necessary to change AXFR to support IXFR.  This assertion has been refuted
> on the grounds that incremental database update does not depend on AXFR,
> since incremental database update does not depend on the underlying wire
> protocol used to create the remote database which is to be modified by
> IXFR. Conceivably, it is unnecessary to use AXFR at all, yet one could
> still use IXFR, so, AXFR is independent of IXFR.

	Nobody is saying that preserving zone content is a *wire*
	issue.  It is a server behaviour issue.

> Some people, many associated with Bind 9 development, assert that AXFR as
> commonly implemented by many implementors over many years, is broken, and
> can't transfer domains correctly.  This claim has been refuted by
> demonstration by interoperability between Bind 8 and other nameserver
> implementations over the years, and 77% of the internet that currently
> does not use Bind 9, yet still does AXFR.

	All this shows is that these nameservers are not used in
	situations where the breakage is demonstrated or the
	administators have learn to work around the breakage or
	choose to live with it or are unaware of it.

> There being no other arguments raised for the Bind 9 AXFR
> clarify/modification proposal, it seems that this proposal is gratuitous
> and unnecessary, and should be rejected.
>
> However, we still have the issue of AXFR ambiguity to deal with, and we
> still need to clarify those ambiguities.  I would therefore like to
> organize a small group of people using implementations other than Bind 9,
> which we declare to be broken, to document the common implementation
> assumptions made, and submit that as a clarification to RFC 1034
> 
> To prevent confusion between the two proposals, I would like to rename the
> first proposal "Bind 9 AXFR Modification", and the second proposal "AXFR
> Clarification". The term "axfr-clarify" will not be used.
> 
> 		--Dean
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Tue Feb 18 22:51:56 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17270;
	Tue, 18 Feb 2003 22:51:56 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lLDg-00030a-00
	for ietf-list@ran.ietf.org; Tue, 18 Feb 2003 22:48:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lLD9-0002yJ-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 22:47:55 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA17011;
	Tue, 18 Feb 2003 22:39:30 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1J3gM4U003505;
	Wed, 19 Feb 2003 14:42:22 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302190342.h1J3gM4U003505@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Tue, 18 Feb 2003 20:58:55 CDT."
             <Pine.LNX.4.44.0302182015150.1529-100000@commander.av8.net> 
Date: Wed, 19 Feb 2003 14:42:22 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Wed, 19 Feb 2003 Mark.Andrews@isc.org wrote:
> 
> > > Good. You found a bug in an implementation. I thought such things were
> > > off-topic for this list.  This bug doesn't mean that AXFR is broken.
> > > Bind 8 did not have this bug, yet it has the common understanding of AXFR
> .
> > >
> > > Let me summarize the discussion:
> > >
> > > Everyone agrees that AXFR specification in RFC 1034 is ambiguous.
> > >
> > > Some people, many associated with Bind 9 development, assert that it is
> > > necessary to change AXFR to support IXFR.  This assertion has been refute
> d
> > > on the grounds that incremental database update does not depend on AXFR,
> > > since incremental database update does not depend on the underlying wire
> > > protocol used to create the remote database which is to be modified by
> > > IXFR. Conceivably, it is unnecessary to use AXFR at all, yet one could
> > > still use IXFR, so, AXFR is independent of IXFR.
> >
> > 	Nobody is saying that preserving zone content is a *wire*
> > 	issue.  It is a server behaviour issue.
> 
> Zone definition and content is not an AXFR issue.  Server administrators
> provide the definition of zone boundaries. (RFC 1034 Section 2.3 and
> elsewhere)  AXFR merely gives the contents of the zone as has been defined
> according to the boundaries and content specified by the administrator.

	Well BIND 9 does this.  CISCO's server does this according
	to John.  BIND 8 doesn't always.  BIND 4 doesn't always.
	DJBDNS doesn't always.  This is independent of the method
	used to transfer the zone to these servers or enter the
	zone contents on these servers.

> The contents could be given to the secondary by FTP or other method.  If
> you mean to change the definition of zone contents, then I would say this
> proposal is hugely mis-labeled.

	It's not changing the definition.  It is preserving the
	definition.

	It's not mis-labeled.  It is stating the implict assumption
	that AXFR transfers what is entered as the zones contents.
	Nothing more, nothing less.

> All the IXFR server needs to do is determine (by some implementation
> dependent, administrator maintained method) what has changed between one
> zone version and another. How it does this is nobody's business but the
> administrator and the implementor. There are infinite possibilities, here.
> One could, for example, store differences in a series of files. The
> administrator could even make the differnce files by hand--this is an
> _implementation detail_. The IXFR server just sends a series or sequences
> consisting of a list of deleted RRs and a list of added RRs to an IXFR
> client. There is nothing more to it. (notwithstanding the optional
> condensation.)

	All of which is irrelevent to this issue.

> The IXFR client must simply make the changes (again, by some
> implementation dependent, administrator maintained method) to the zone by
> deleting RRs and adding RR's in each sequence. The original version of the
> zone might have been obtained by FTP (or quantum interference, or the
> psychic network) for all we know.

	Well the problem is that you have to get the *original* version,
	not a corrupted version.  AXFR implementations are not returning
	the data originally entered.
 
> This isn't rocket science, and doesn't require any AXFR changes. Nor does
> it require that the zone boundaries be defined only in some certain way,
> beyond the definition of zone boundaries given by the system
> administrator.

	It does however require that for a given serial number that all
	sources of the zone have supplied identical contents.  You should
	be able to apply a IXFR delta to a copy derived from any source
	and have it apply without error.
 
> > > Some people, many associated with Bind 9 development, assert that AXFR as
> > > commonly implemented by many implementors over many years, is broken, and
> > > can't transfer domains correctly.  This claim has been refuted by
> > > demonstration by interoperability between Bind 8 and other nameserver
> > > implementations over the years, and 77% of the internet that currently
> > > does not use Bind 9, yet still does AXFR.
> >
> > 	All this shows is that these nameservers are not used in
> > 	situations where the breakage is demonstrated or the
> > 	administators have learn to work around the breakage or
> > 	choose to live with it or are unaware of it.
> 
> "administrators have learn[ed] to work around [it,...] live with it [,] or
> are unaware of it".  Agreed.  Having done so, we don't want to stir the
> pot.

	LOL.
 
> Essentially, you are putting more (unnecessary) constraints on
> implementations, and thus on the administrators, who are supposed to be
> pretty free to define the zone boundaries.  Of course, the specifics of an
> implementation puts some constraints on the adminstrator, but the
> administrator can choose a different implementation more to her liking.

	The constaint was already there and it is necessary for reliable
	operation of the DNS.
 
> These unnecessary constraints are a "bad thing".
>
> > > To prevent confusion between the two proposals, I would like to rename th
> e
> > > first proposal "Bind 9 AXFR Modification", and the second proposal "AXFR
> > > Clarification". The term "axfr-clarify" will not be used.
> 
> I presume agreement on the name change?

	No.
> 
> 		--Dean
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 00:49:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19343;
	Wed, 19 Feb 2003 00:49:31 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lN6m-0004X3-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 00:49:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lN6L-0004WV-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 00:49:01 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19269
	for <ietf@ietf.org>; Wed, 19 Feb 2003 00:40:39 -0500 (EST)
Received: (qmail 19703 invoked by uid 1016); 19 Feb 2003 05:44:54 -0000
Date: 19 Feb 2003 05:44:54 -0000
Message-ID: <20030219054454.19702.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: axfr-clarify breaking RFC 1034
References: <20030215110946.67446.qmail@cr.yp.to> <200302151239.h1FCdCd6028798@drugs.dv.isc.org> <20030217204351.GB16887@thales.memphis.edu> <3E5156B7.3060508@daimlerchrysler.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Kevin Darcy writes:
> RFC 1034 requires matching NS record sets in the parent 
> and the child, but this cannot be *guaranteed*

In the situation under discussion, one server has both zones, so that
server _can_ guarantee RFC 1034 consistency---and my server _does_.
(BIND 8 also does, to some extent. BIND 9 doesn't.)

Andrews says that this RFC 1034 enforcement causes problems for a system
administrator who tries to violate RFC 1034. Well, that's too damn bad!
The system administrator shouldn't be trying to violate RFC 1034.

If the BIND company wants the RFC 1034 rule changed, they can propose
that, and we'll discuss the costs and benefits. Instead they're trying
to slip the change past us as a ``clarification.'' You know they're
lying; why are you condoning dishonest behavior?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 01:33:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20156;
	Wed, 19 Feb 2003 01:33:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lNpJ-0005d2-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 01:35:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lNoL-0005cI-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 01:34:29 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20038
	for <ietf@ietf.org>; Wed, 19 Feb 2003 01:26:07 -0500 (EST)
Received: (qmail 39959 invoked by uid 1016); 19 Feb 2003 06:30:22 -0000
Date: 19 Feb 2003 06:30:22 -0000
Message-ID: <20030219063022.39958.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: axfr-clarify breaking RFC 1034, continued
References: <20030217202833.GA16887@thales.memphis.edu> <200302180227.h1I2RSd6053173@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> ; <<>> DiG 9.3.0s20021115 <<>> axfr child.example.net @10.53.0.2
  [ claims that ns2.child.example.net doesn't exist, as compared to: ]
> ; <<>> DiG 9.3.0s20021115 <<>> axfr example.net @10.53.0.2
> ns2.child.example.net.	10	IN	A	10.53.0.2

Once again: That configuration violates RFC 1034. Specifically, sections
4.2.1 and 4.2.2 of RFC 1034 make crystal clear that the ns2 glue in the
parent zone is supposed to match the data in the child zone.

My software enforces the RFC 1034 requirement in this situation. If it
had been running on 10.53.0.2 then you wouldn't have been able to screw
up the configuration in the first place.

What you're complaining about is my software's perfectly straightforward
enforcement of the RFC 1034 requirement on the client side after you set
up an RFC-1034-violating configuration with your server. Is it really so
difficult to understand that it's your fault for violating RFC 1034?

  [ complaining about zone transfers in tinydns ]
> You have to roll your own from what I can see.

No, you don't. Have you ever heard of ``third parties''? How about
``interchangeable parts''? Monolithic design is good for a company
trying to achieve lock-in, but modular design leads to faster evolution
and, in the end, better software for the users.

If you're trying to say that I haven't bothered to write up the existing
AXFR tools on my web pages, you're right. These tools have an extremely
limited audience; I have better things to do. The vast majority of users
are much happier with rsync+ssh than they would ever be with anything
based on AXFR. See http://cr.yp.to/djbdns/tcp.html#intro-axfr.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 02:04:27 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26403;
	Wed, 19 Feb 2003 02:04:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lOGP-0006Rm-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 02:03:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lOFS-0006Qx-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 02:02:30 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20403
	for <ietf@ietf.org>; Wed, 19 Feb 2003 01:54:06 -0500 (EST)
Received: (qmail 50064 invoked by uid 1016); 19 Feb 2003 06:58:22 -0000
Date: 19 Feb 2003 06:58:22 -0000
Message-ID: <20030219065822.50063.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <200302142024.h1EKOkS10983@guava.araneus.fi> <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net> <200302150157.h1F1vXw11389@guava.araneus.fi> <3E52AEB2.2040807@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Josh Littlefield writes:
> RFC1034 clearly states that the answer section "carries RRs which
> directly answer the query."  I don't see how anyone could conclude
> that AXFR clients should look for zone RRs anywhere else.

There is overwhelming consensus that (in the absence of extended
behavior requested by the client) the AXFR _server_ must leave the
additional section and authority section empty. It must put the data
into the answer section. All existing servers work this way---and must
do so for interoperability.

There are several perfectly valid parsing strategies for the client.
In particular, my software uses the simple strategy

   while there are records left
      read a record

while BIND 9 uses the slightly more complicated strategy

   while there are records left in the answer section
      read a record

Both strategies work, since servers put all records into the answer
section. Neither strategy creates any interoperability problems.

There is certainly _not_ consensus on telling the _client_ to use the
BIND 9 strategy. Furthermore, any such statement (whether ``MUST'' or
``SHOULD'') would blatantly violate RFC 2119, section 6.

This is about the tenth time that I have had to point out the blazingly
obvious fact that constraining _server_ behavior is not the same as
constraining _client_ behavior.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 04:54:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17266;
	Wed, 19 Feb 2003 04:54:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lQs0-0000hv-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 04:50:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lQru-0000hS-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 04:50:22 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17060;
	Wed, 19 Feb 2003 04:41:54 -0500 (EST)
Received: from delta.cs.mu.OZ.AU ([172.30.0.189])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1J9jKd28424;
	Wed, 19 Feb 2003 16:45:21 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1J9gOK05421;
	Wed, 19 Feb 2003 16:42:25 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034 
In-Reply-To: <20030219054454.19702.qmail@cr.yp.to> 
References: <20030219054454.19702.qmail@cr.yp.to>  <20030215110946.67446.qmail@cr.yp.to> <200302151239.h1FCdCd6028798@drugs.dv.isc.org> <20030217204351.GB16887@thales.memphis.edu> <3E5156B7.3060508@daimlerchrysler.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Feb 2003 16:42:23 +0700
Message-ID: <5419.1045647743@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        19 Feb 2003 05:44:54 -0000
    From:        "D. J. Bernstein" <djb@cr.yp.to>
    Message-ID:  <20030219054454.19702.qmail@cr.yp.to>

  | In the situation under discussion, one server has both zones, so that
  | server _can_ guarantee RFC 1034 consistency---and my server _does_.
  | (BIND 8 also does, to some extent. BIND 9 doesn't.)

There are two requirements (in this general area) on servers in the DNS.
One is that two servers for the same zone give the same answers to the
same questions (except in the interval between an update to one server
and its being made known to the other, during which time the SOA serial
numbers will differ).   (AXFR is one such possible question).

Second, glue records should be copied from the authoritative zone to the
parent, so they are the same in both zones.   Again, there is necessarily
going to sometimes be a delay between when the child zone is updated and
when the parent is updated.

Your reading of the requirements means that in order to shorten the
delay in the second case, in some circumstances, you're willing to generate
cases where the first incompatibility (servers for the same zone returning
different answers) will exist, without the serial numbers differing (and
with no defined method of reconciling the issue - that is, there is no
way of knowing which answer is the "correct" one).

In the parent/child case, if there is a difference, the child's answers are
correct by definition.   In the "different zones after an update" case, the
server with the higher serial number is correct, the lower is out of date.
In the case we have been discussing, the answers differ, both servers are
serving the same zone, the serial numbers are the same, which answer should
be used?   How can anyone guess?

Just about everyone here seems to be convinced that the (negligible) gain
to be gained from forcing the parent and child to contain the same records
in the cases where that is feasible is not worth the kind of problems this
can cause to the first requirement (which in hard cases can actually be
difficult to fix without manual intervention - it won't always just "fix
itself" though normal correct operation of the servers).   The requirements
you're insisting upon enforcing in your servers trivially fix themselves
when the parent zone is updated (remember you assume that if the human
doesn't do that, any problems are of their own making...)

If you have a proposal for some method to actually cause the parent/child
delegation to *always* be compatible (glue in parent matches records in child,
always), then please don't keep it a secret, I'd really like to see it.

Until then, assuming that this will always be true, and writing off all
other cases as "configuration error, anything is allowed to happen" is
inappropriate.

kre




From owner-ietf@ietf.org  Wed Feb 19 08:43:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24736;
	Wed, 19 Feb 2003 08:43:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lUWY-00037o-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 08:44:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lUVK-00033Q-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 08:43:18 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA24526;
	Wed, 19 Feb 2003 08:34:48 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1JDcC4U004904;
	Thu, 20 Feb 2003 00:38:13 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302191338.h1JDcC4U004904@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "19 Feb 2003 06:58:22 -0000."
             <20030219065822.50063.qmail@cr.yp.to> 
Date: Thu, 20 Feb 2003 00:38:12 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Josh Littlefield writes:
> > RFC1034 clearly states that the answer section "carries RRs which
> > directly answer the query."  I don't see how anyone could conclude
> > that AXFR clients should look for zone RRs anywhere else.
> 
> There is overwhelming consensus that (in the absence of extended
> behavior requested by the client) the AXFR _server_ must leave the
> additional section and authority section empty. It must put the data
> into the answer section. All existing servers work this way---and must
> do so for interoperability.
> 
> There are several perfectly valid parsing strategies for the client.
> In particular, my software uses the simple strategy
> 
>    while there are records left
>       read a record

	Which can only be found by adding up the three fields in
	the header (number of answer  records (which bind uses),
	number of records in the authority section and number of
	records in the additional section).  You can't use the DNS
	message length as too many implementations get it wrong and
	leave a couple of bytes between the end of the messages as
	discovered by processing the records and the end of the
	data that is read.  You have discovered this havn't you?
 
> while BIND 9 uses the slightly more complicated strategy

	BIND has always used the simple strategy of reading the
	number from the header then processing that number of
	records after skipping any questions, again read from
	the header.
 
>    while there are records left in the answer section
>       read a record

	Let me see if I have your logic right,
	
	Simple:
	Read the number of questions then skip them. Read three
	numbers, add them up, then read this number of records.
	
	Complicated:
	Read the number of questions then skip them. Read one
	number then read this number of records.

	I think you have the labels the wrong way around.

> Both strategies work, since servers put all records into the answer
> section. Neither strategy creates any interoperability problems.

	There is different behaviour.  That is enough reason in and
	of itself to clarify the issue.

	I don't think anyone envisioned someone that would process
	records outside of the answer section as answers.

> There is certainly _not_ consensus on telling the _client_ to use the
> BIND 9 strategy. Furthermore, any such statement (whether ``MUST'' or
> ``SHOULD'') would blatantly violate RFC 2119, section 6.
> 
> This is about the tenth time that I have had to point out the blazingly
> obvious fact that constraining _server_ behavior is not the same as
> constraining _client_ behavior.

	
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 10:01:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26821;
	Wed, 19 Feb 2003 10:01:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lVe9-00069I-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 09:56:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lVdq-00068R-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 09:56:11 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26323;
	Wed, 19 Feb 2003 09:47:42 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h1JEqAw06492;
	Wed, 19 Feb 2003 09:52:10 -0500
Date: Wed, 19 Feb 2003 09:52:10 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: <ietf@ietf.org>, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify breaking RFC 1034
In-Reply-To: <20030219054454.19702.qmail@cr.yp.to>
Message-ID: <Pine.LNX.4.33.0302190951010.29701-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On 19 Feb 2003, D. J. Bernstein wrote:

> If the BIND company wants the RFC 1034 rule changed, they can propose
> that, and we'll discuss the costs and benefits. Instead they're trying
> to slip the change past us as a ``clarification.'' You know they're
> lying; why are you condoning dishonest behavior?

maybe it's because the bind company is a vixie thingy.  and we all know a
good portion of the i$ociety owe saint vixie.

regards
joe baptista




From owner-ietf@ietf.org  Wed Feb 19 13:04:10 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03376;
	Wed, 19 Feb 2003 13:04:10 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lYRN-0001V3-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 12:55:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lYQl-0001U8-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 12:54:51 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA02886
	for <ietf@ietf.org>; Wed, 19 Feb 2003 12:46:22 -0500 (EST)
Received: (qmail 55141 invoked by uid 1016); 19 Feb 2003 17:50:37 -0000
Date: 19 Feb 2003 17:50:37 -0000
Message-ID: <20030219175037.55139.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030219065822.50063.qmail@cr.yp.to> <200302191338.h1JDcC4U004904@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> You can't use the DNS message length as too many implementations get
> it wrong and leave a couple of bytes between the end of the messages
> as discovered by processing the records and the end of the data that
> is read.

False. The Microsoft AXFR _client_ puts two extra bytes after its AXFR
requests to indicate its support for multiple records per DNS packet,
but the Microsoft AXFR _server_ does nothing of the sort. My AXFR client
can and does use the packet length, in full compliance with RFC 1035.
There are no interoperability problems here.

(By the way, my DNS software is more widely deployed than Microsoft's,
and much more stable, so if there were an interoperability problem then
the lowest-cost solution would be to redeploy Microsoft's software. But
these problems are a figment of your imagination.)

> There is different behaviour.  That is enough reason in and
> of itself to clarify the issue.

False premise, bad logic, false conclusion. These software differences
don't affect interoperability, so they are none of the IETF's business.
See RFC 2119, section 6.

> I don't think anyone envisioned someone that would process
> records outside of the answer section as answers.

Read the full DNS standards, RFC 1034 and RFC 1035. Example: To save
time, the additional section of an MX response usually contains A
records that are reported as answers to subsequent queries. This is
perfectly standard behavior not only in theory but also in practice.

(To the extent that proposed standard RFC 2181 suggests otherwise, RFC
2181 is out of whack with reality, and RFC 2181 will have to be fixed.)

You can't seriously promote a ``never treat additional records as
answers'' religion when every major DNS cache---including BIND 9---
blatantly violates that religion. If you start adding qualifiers such as
``except in MX queries'' then your religion starts to sound really dumb.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 13:06:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03482;
	Wed, 19 Feb 2003 13:06:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lYdy-0001hh-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 13:08:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lYdF-0001gn-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 13:07:45 -0500
Received: from smtp018.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03246
	for <ietf@ietf.org>; Wed, 19 Feb 2003 12:59:15 -0500 (EST)
Received: from 212.68.224.51.brutele.be (HELO toto) (Tomson?Eric@212.68.224.51 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 19 Feb 2003 18:03:02 -0000
Reply-To: <Tomson_Eric@Yahoo.fr>
From: "Tomson Eric \(Yahoo.fr\)" <Tomson_Eric@Yahoo.fr>
To: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>
Cc: <ietf@ietf.org>, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Just three questions
Date: Wed, 19 Feb 2003 19:05:09 +0100
Organization: Eric Tomson
Message-ID: <002d01c2d841$726dd670$1100a8c0@tomson.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <Pine.LNX.4.33.0302190951010.29701-100000@dot-god.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA03248
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA03482

Just three questions :

1/does the IETF support or contest the "Inclusive Name Space" (the one
operated by NewRoot instead of the ICANN)?

2/is this list reserved for all IETF-supporting people only, or is it
also open to IETF opponents/challengers?

3/knowing that the Internet Society is the only official body amongst
all the Internet-related structures (IETF, IAB, IESG, etc.), created to
host all of them, is it decent and acceptable to dispute/oppose/mock it,
here in this list?

Just asking...

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com



From owner-ietf@ietf.org  Wed Feb 19 14:07:31 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05288;
	Wed, 19 Feb 2003 14:07:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lZLW-0003E4-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 13:53:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lZKe-0003DB-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 13:52:36 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04506;
	Wed, 19 Feb 2003 13:44:05 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6DD366259E; Wed, 19 Feb 2003 19:47:53 +0100 (CET)
Date: Wed, 19 Feb 2003 19:47:53 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tomson_Eric@Yahoo.fr
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Just three questions
Message-ID: <582310000.1045680473@askvoll.hjemme.alvestrand.no>
In-Reply-To: <002d01c2d841$726dd670$1100a8c0@tomson.be>
References:  <002d01c2d841$726dd670$1100a8c0@tomson.be>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On onsdag, februar 19, 2003 19:05:09 +0100 "Tomson Eric (Yahoo.fr)" 
<Tomson_Eric@Yahoo.fr> wrote:

> Just three questions :
>
> 1/does the IETF support or contest the "Inclusive Name Space" (the one
> operated by NewRoot instead of the ICANN)?

See RFC 2826; the IAB thinks that one root is enough.

> 2/is this list reserved for all IETF-supporting people only, or is it
> also open to IETF opponents/challengers?

You have adressed three lists.

ietf@ietf.org exists as an open forum to further the work of the IETF.
  Its charter can be found on http://www.ietf.org/maillist.html
iesg@ietf.org exists to communicate with the Internet Engineering Steering
  Group (IESG).
namedroppers@ops.ietf.org exists as an open forum to further the work
  of the DNSEXT IETF working group, described in
  http://www2.ietf.org/html.charters/dnsext-charter.html

None of the lists restrict who can post to it (apart from spam control).
On both of the open lists, repeated posting of material irrelevant to the 
purpose of the list can lead to your posting privilleges being restricted.

This has nothing to do with what you think, or say, and everything to do 
with the forum in which you choose to say it.

> 3/knowing that the Internet Society is the only official body amongst
> all the Internet-related structures (IETF, IAB, IESG, etc.), created to
> host all of them, is it decent and acceptable to dispute/oppose/mock it,
> here in this list?

Since the IETF list (ietf@ietf.org) is intended as a forum to disucss the 
policies of the IETF (among other things), reasoned opinions about the 
relationship between the IETF and ISOC is a valid subject for this list, no 
matter whether the person stating that opinion thinks that the relationship 
is a good thing or a bad thing.

However, it would be inappropriate to the purpose of the namedroppers list.

Mockery is not generally considered a reasoned form of opinion.

Did this answer your question?

                    Harald Alvestrand




From owner-ietf@ietf.org  Wed Feb 19 14:09:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05406;
	Wed, 19 Feb 2003 14:09:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lZcw-0003ZV-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 14:11:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lZci-0003Xn-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 14:11:16 -0500
Received: from htt-consult.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05177
	for <IETF@ietf.org>; Wed, 19 Feb 2003 14:02:45 -0500 (EST)
Received: from port3490.htt-consult.com ([65.84.78.209]) by htt-consult.com ; Wed, 19 Feb 2003 14:06:32 -0500
Message-Id: <5.1.0.14.2.20030219110511.031e9e28@localhost>
X-Sender: rgm-ietf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 19 Feb 2003 11:06:18 -0800
To: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Dave Crocker <dhc2@dcrocker.net>, ietf <IETF@ietf.org>
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Subject: Re: November IETF dates
In-Reply-To: <6640000.1045570828@askvoll.hjemme.alvestrand.no>
References: <8991122056.20030215092836@brandenburg.com>
 <8991122056.20030215092836@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Rcpt-To: <IETF@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:20 PM 2/18/2003 +0100, Harald Tveit Alvestrand wrote:

>November is already signed.

And the same week as the IEEE 802 plenary  :(

Looks like the first IETF in N.A. that I will totally miss.

Of course I am missing most of the San Fran IETF as it falls over the 
holiday of Purim.

Sigh.






From owner-ietf@ietf.org  Wed Feb 19 14:30:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06060;
	Wed, 19 Feb 2003 14:30:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lZyE-00054a-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 14:33:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lZy7-00053S-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 14:33:23 -0500
Received: from sleekfreak.ath.cx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05837;
	Wed, 19 Feb 2003 14:24:51 -0500 (EST)
Received: from localhost ([127.0.0.1] ident=shogunx)
	by sleekfreak.ath.cx with esmtp (Exim 3.35 #1 (Debian))
	id 18lNiW-0003J9-00; Wed, 19 Feb 2003 01:28:28 -0500
Date: Wed, 19 Feb 2003 01:28:15 -0500 (EST)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "Tomson Eric (Yahoo.fr)" <Tomson_Eric@Yahoo.fr>
cc: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>, <ietf@ietf.org>,
        <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: Just three questions
In-Reply-To: <002d01c2d841$726dd670$1100a8c0@tomson.be>
Message-ID: <Pine.LNX.4.44.0302190122210.9708-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id OAA06060

On Wed, 19 Feb 2003, Tomson Eric (Yahoo.fr) wrote:

> Just three questions :
>
> 1/does the IETF support or contest the "Inclusive Name Space" (the one
> operated by NewRoot instead of the ICANN)?

Dont forget the opennic www.opennic.unrated.net the pacificroot
pacificroot.org or the open root server consortium www.open-rsc.org when
addressing the topic of alternative root servers.  Notwithstanding, the
IETF is made up of individuals, each with their own perspectives and
opinions.

>
> 2/is this list reserved for all IETF-supporting people only, or is it
> also open to IETF opponents/challengers?
>

Without this list, and the IETF, you would not be able to send the email I
am responding to.

> 3/knowing that the Internet Society is the only official body amongst
> all the Internet-related structures (IETF, IAB, IESG, etc.), created to
> host all of them, is it decent and acceptable to dispute/oppose/mock it,
> here in this list?
>

Dispute all you want, if the topic is valid.  Oppose whatever you choose.
It is never a wise idea, however, to mock on of the most intelligent
collections of individuals on the planet.  Just a word to the wise.

Scott

> Just asking...
>
> ___________________________________________________________
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> Yahoo! Mail : http://fr.mail.yahoo.com
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from daytona beach
http://sleekfreak.ath.cx




From owner-ietf@ietf.org  Wed Feb 19 14:56:47 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05282;
	Wed, 19 Feb 2003 14:07:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lZY6-0003Qw-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 14:06:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lZXH-0003Q5-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 14:05:39 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04980
	for <ietf@ietf.org>; Wed, 19 Feb 2003 13:57:09 -0500 (EST)
Received: (qmail 8909 invoked by uid 1016); 19 Feb 2003 19:01:24 -0000
Date: 19 Feb 2003 19:01:24 -0000
Message-ID: <20030219190124.8908.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034
References: <20030219054454.19702.qmail@cr.yp.to> <20030215110946.67446.qmail@cr.yp.to> <200302151239.h1FCdCd6028798@drugs.dv.isc.org> <20030217204351.GB16887@thales.memphis.edu> <3E5156B7.3060508@daimlerchrysler.com> <5419.1045647743@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Robert Elz writes:
> If you have a proposal for some method to actually cause the parent/child
> delegation to *always* be compatible (glue in parent matches records in
> child, always), then please don't keep it a secret

Read about timestamps in http://cr.yp.to/djbdns/tinydns-data.html. It's
not my fault that BIND can't handle this trivial synchronization.

If you're trying to say that the RFC 1034 requirement should be loosened
to allow semi-synchronized changes (parent zone is changed after all the
child servers have changed), go ahead and make that proposal in DNSEXT,
and we'll discuss it. But don't try to sneak it past us as part of an
``AXFR clarification.''

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 16:35:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09520;
	Wed, 19 Feb 2003 16:35:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lbrJ-0000y2-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 16:34:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lbqU-0000x9-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 16:33:38 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09147;
	Wed, 19 Feb 2003 16:25:03 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1JLSc4U005926;
	Thu, 20 Feb 2003 08:28:38 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302192128.h1JLSc4U005926@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "19 Feb 2003 17:50:37 -0000."
             <20030219175037.55139.qmail@cr.yp.to> 
Date: Thu, 20 Feb 2003 08:28:38 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Mark.Andrews@isc.org writes:
> > You can't use the DNS message length as too many implementations get
> > it wrong and leave a couple of bytes between the end of the messages
> > as discovered by processing the records and the end of the data that
> > is read.
> 
> False. The Microsoft AXFR _client_ puts two extra bytes after its AXFR
> requests to indicate its support for multiple records per DNS packet,
> but the Microsoft AXFR _server_ does nothing of the sort. My AXFR client
> can and does use the packet length, in full compliance with RFC 1035.
> There are no interoperability problems here.

	Well you havn't struck the servers that get this calculation
	wrong yet.  However I don't find that suprising as your server
	really isn't designed to with AXFR in mind.
 
> (By the way, my DNS software is more widely deployed than Microsoft's,
> and much more stable, so if there were an interoperability problem then
> the lowest-cost solution would be to redeploy Microsoft's software. But
> these problems are a figment of your imagination.)

	I never said that Microsoft was the responible vendor.  I've
	never bothered to find the name of the vendor.
 
> > There is different behaviour.  That is enough reason in and
> > of itself to clarify the issue.
> 
> False premise, bad logic, false conclusion. These software differences
> don't affect interoperability, so they are none of the IETF's business.
> See RFC 2119, section 6.

	But it does affect interopability with servers that get
	things slightly wrong.

	You can't trust the UDP length and you can't trust the TCP
	message size to find the end of reply received.  There are
	servers that get these calculations wrong.
 
> > I don't think anyone envisioned someone that would process
> > records outside of the answer section as answers.
> 
> Read the full DNS standards, RFC 1034 and RFC 1035. Example: To save
> time, the additional section of an MX response usually contains A
> records that are reported as answers to subsequent queries. This is
> perfectly standard behavior not only in theory but also in practice.

	The additional section does NOT contain the answer.  It
	contains other data that may be related however it is not
	part of the answer to the question an is not treated as
	such.

> (To the extent that proposed standard RFC 2181 suggests otherwise, RFC
> 2181 is out of whack with reality, and RFC 2181 will have to be fixed.)
> 
> You can't seriously promote a ``never treat additional records as
> answers'' religion when every major DNS cache---including BIND 9---
> blatantly violates that religion. If you start adding qualifiers such as
> ``except in MX queries'' then your religion starts to sound really dumb.

	We selectively cache the contents of the additional section.
	We also reject what shouldn't be there or what we don't
	trust the current server to give us.

	Mark
 
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 18:26:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12587;
	Wed, 19 Feb 2003 18:26:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lde7-0005OL-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 18:28:59 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ldbK-0005M3-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 18:26:06 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12385;
	Wed, 19 Feb 2003 18:17:30 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1JNL94U006491;
	Thu, 20 Feb 2003 10:21:10 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302192321.h1JNL94U006491@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify breaking RFC 1034 
In-reply-to: Your message of "19 Feb 2003 19:01:24 -0000."
             <20030219190124.8908.qmail@cr.yp.to> 
Date: Thu, 20 Feb 2003 10:21:09 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Robert Elz writes:
> > If you have a proposal for some method to actually cause the parent/child
> > delegation to *always* be compatible (glue in parent matches records in
> > child, always), then please don't keep it a secret
> 
> Read about timestamps in http://cr.yp.to/djbdns/tinydns-data.html. It's
> not my fault that BIND can't handle this trivial synchronization.
> 
> If you're trying to say that the RFC 1034 requirement should be loosened
> to allow semi-synchronized changes (parent zone is changed after all the
> child servers have changed), go ahead and make that proposal in DNSEXT,
> and we'll discuss it. But don't try to sneak it past us as part of an
> ``AXFR clarification.''

	Semi-synchronized changes have always been part of the DNS.
	Anyone who believes otherwise is deluding themselves.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 19:02:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13272;
	Wed, 19 Feb 2003 19:02:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18leBV-00068u-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 19:03:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18leAq-00068D-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 19:02:48 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA13097;
	Wed, 19 Feb 2003 18:54:08 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1JNuj4U006653;
	Thu, 20 Feb 2003 10:56:47 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302192356.h1JNuj4U006653@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Wed, 19 Feb 2003 16:32:01 CDT."
             <Pine.LNX.4.44.0302191621400.6276-100000@commander.av8.net> 
Date: Thu, 20 Feb 2003 10:56:45 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> 
> 
> On Wed, 19 Feb 2003 Mark.Andrews@isc.org wrote:
> 
> > > All the IXFR server needs to do is determine (by some implementation
> > > dependent, administrator maintained method) what has changed between one
> > > zone version and another. How it does this is nobody's business but the
> > > administrator and the implementor. There are infinite possibilities, here
> .
> > > One could, for example, store differences in a series of files. The
> > > administrator could even make the differnce files by hand--this is an
> > > _implementation detail_. The IXFR server just sends a series or sequences
> > > consisting of a list of deleted RRs and a list of added RRs to an IXFR
> > > client. There is nothing more to it. (notwithstanding the optional
> > > condensation.)
> >
> > 	All of which is irrelevent to this issue.
> 
> THAT's what I have been saying. You were the one who said we needed to do
> this to support IXFR. I've been saying that claim was wrong. Thanks for
> FINALLY coming round to that.
> 
> > > The IXFR client must simply make the changes (again, by some
> > > implementation dependent, administrator maintained method) to the zone by
> > > deleting RRs and adding RR's in each sequence. The original version of th
> e
> > > zone might have been obtained by FTP (or quantum interference, or the
> > > psychic network) for all we know.
> >
> > 	Well the problem is that you have to get the *original* version,
> > 	not a corrupted version.  AXFR implementations are not returning
> > 	the data originally entered.
> 
> They sure have been.

	Not always.
 
> > > This isn't rocket science, and doesn't require any AXFR changes. Nor does
> > > it require that the zone boundaries be defined only in some certain way,
> > > beyond the definition of zone boundaries given by the system
> > > administrator.
> >
> > 	It does however require that for a given serial number that all
> > 	sources of the zone have supplied identical contents.  You should
> > 	be able to apply a IXFR delta to a copy derived from any source
> > 	and have it apply without error.
> 
> None of this is relevant. All that is necessary is to delete the RRs, and
> insert the RRs in the sequence.
> 
> If the zones are inconsistent through administrative mistake, then it
> won't matter what the IXFR does.

	Who said anything administrative mistakes?  The content is being
	unilaterally changed by the servers.
 
> > > > > Some people, many associated with Bind 9 development, assert that AXF
> R as
> > > > > commonly implemented by many implementors over many years, is broken,
>  and
> > > > > can't transfer domains correctly.  This claim has been refuted by
> > > > > demonstration by interoperability between Bind 8 and other nameserver
> > > > > implementations over the years, and 77% of the internet that currentl
> y
> > > > > does not use Bind 9, yet still does AXFR.
> > > >
> > > > 	All this shows is that these nameservers are not used in
> > > > 	situations where the breakage is demonstrated or the
> > > > 	administators have learn to work around the breakage or
> > > > 	choose to live with it or are unaware of it.
> > >
> > > "administrators have learn[ed] to work around [it,...] live with it [,] o
> r
> > > are unaware of it".  Agreed.  Having done so, we don't want to stir the
> > > pot.
> >
> > 	LOL.
> 
> Strange, that was my reaction, too. I'm just trying to be polite.  77%
> work just fine. We don't want to break 77% of the servers out there.

	You really think that it will break those servers?  LOL.
 
> > > Essentially, you are putting more (unnecessary) constraints on
> > > implementations, and thus on the administrators, who are supposed to be
> > > pretty free to define the zone boundaries.  Of course, the specifics of a
> n
> > > implementation puts some constraints on the adminstrator, but the
> > > administrator can choose a different implementation more to her liking.
> >
> > 	The constaint was already there and it is necessary for reliable
> > 	operation of the DNS.
> 
> No, you ware not being honest about the contents of the Draft. See my last
> message to Andreas.

	The abstract say:

				    This memo clarifies, updates, and
   adds missing detail to the original AXFR protocol specification in
   RFC1034.

	I fail to see how the contents can be deemed misleading when
	it states up front what it does.  Woops we missed warning you
	up front that it contains a warning.
 
> > > > > To prevent confusion between the two proposals, I would like to renam
> e th
> > > e
> > > > > first proposal "Bind 9 AXFR Modification", and the second proposal "A
> XFR
> > > > > Clarification". The term "axfr-clarify" will not be used.
> > >
> > > I presume agreement on the name change?
> >
> > 	No.
> 
> Then the entire draft should be rejected since it is misleading.  Please
> resubmit a proposal that isn't misleading the community about its purpose,
> impact, and contents.
> 
> 		--Dean

	
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 19:08:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13551;
	Wed, 19 Feb 2003 19:08:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18leKD-0006dS-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 19:12:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18leJu-0006ca-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 19:12:10 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13348
	for <ietf@ietf.org>; Wed, 19 Feb 2003 19:03:37 -0500 (EST)
Received: (qmail 38145 invoked by uid 1016); 20 Feb 2003 00:07:52 -0000
Date: 20 Feb 2003 00:07:52 -0000
Message-ID: <20030220000752.38144.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034
References: <20030219190124.8908.qmail@cr.yp.to> <200302192321.h1JNL94U006491@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> Semi-synchronized changes have always been part of the DNS.

If there's an honest proposal to modify the DNS specifications to allow
semi-synchronized changes (once again: parent zone being changed after
all the child servers have changed), perhaps the discussion will reveal
that those changes work with BIND 4, BIND 8, djbdns, etc.; that those
changes are useful; and that nobody objects to this modification.

On the other hand, if there's an honest proposal to modify the DNS
specifications to allow _unsychronized_ changes (such as your asinine
configuration examples), the discussion will reveal that those changes
do _not_ work with the majority of DNS servers on the Internet, that
those changes are _not_ useful, and that the modification is a bad idea.

What we have here is much worse: a thoroughly dishonest attempt to slip
the latter modification past us as part of an ``AXFR clarification.''
Anyone with a shred of integrity should be opposing this fraud.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Wed Feb 19 21:32:21 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15952;
	Wed, 19 Feb 2003 21:32:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lgUi-00009R-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 21:31:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lgU7-00008x-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 21:30:51 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA15782;
	Wed, 19 Feb 2003 21:22:14 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1K2Pp4U007052;
	Thu, 20 Feb 2003 13:25:52 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302200225.h1K2Pp4U007052@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify breaking RFC 1034 
In-reply-to: Your message of "20 Feb 2003 00:07:52 -0000."
             <20030220000752.38144.qmail@cr.yp.to> 
Date: Thu, 20 Feb 2003 13:25:51 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Mark.Andrews@isc.org writes:
> > Semi-synchronized changes have always been part of the DNS.
> 
> If there's an honest proposal to modify the DNS specifications to allow
> semi-synchronized changes (once again: parent zone being changed after
> all the child servers have changed), perhaps the discussion will reveal
> that those changes work with BIND 4, BIND 8, djbdns, etc.; that those
> changes are useful; and that nobody objects to this modification.
>
> On the other hand, if there's an honest proposal to modify the DNS
> specifications to allow _unsychronized_ changes (such as your asinine
> configuration examples), the discussion will reveal that those changes
> do _not_ work with the majority of DNS servers on the Internet, that
> those changes are _not_ useful, and that the modification is a bad idea.
>
> What we have here is much worse: a thoroughly dishonest attempt to slip
> the latter modification past us as part of an ``AXFR clarification.''
> Anyone with a shred of integrity should be opposing this fraud.

	If you want synchronized changes in the parent and child
	zones you need to write up a draft to explain how to do it.
	The current DNS does not have this capability.

	I would suggest that you will need to add inception and
	expiration times as meta data for each RR.

	I will be happy to review the draft when you make it available.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Wed Feb 19 22:47:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18149;
	Wed, 19 Feb 2003 22:47:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lhfI-0005Nc-00
	for ietf-list@ran.ietf.org; Wed, 19 Feb 2003 22:46:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lhey-0005N5-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 22:46:08 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA17515
	for <ietf@ietf.org>; Wed, 19 Feb 2003 22:37:32 -0500 (EST)
Received: (qmail 14685 invoked by uid 1016); 20 Feb 2003 03:41:48 -0000
Date: 20 Feb 2003 03:41:48 -0000
Message-ID: <20030220034148.14684.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034
References: <20030220000752.38144.qmail@cr.yp.to> <200302200225.h1K2Pp4U007052@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Here's a chart summarizing the situation:

   Timing of         |Useful in|RFC 1034 |BIND 8 |BIND 9 |tinydns
   data change       |practice |compliant|support|support|support
   ------------------+---------+---------+-------+-------+-------
   Synchronized      |Yes      |Yes      |No     |No     |Yes
   Semi-synchronized |Yes      |No       |Yes    |Yes    |Yes
   Unsynchronized    |No       |No       |No     |Yes    |No

The BIND company observes that

   * synchronized changes are hard to do with BIND, even though they're
     required by RFC 1034; and
   * unsynchronized changes can fail miserably with BIND 8 et al., which
     account for the majority of DNS servers.

The obvious solution is semi-synchronized changes, which work with the
entire installed base. I wouldn't object to modifying RFC 1034 to allow
semi-synchronized changes.

(To repeat the relevant definitions: A synchronized change happens at
the same time in all the parent servers and all the child servers. A
semi-synchronized change happens in the parent zone---specifically, the
parent serial is changed---after it happens in all the child servers.)

I certainly _do_ object to allowing unsynchronized changes. They don't
work correctly with the installed base, and they have no advantages over
semi-synchronized changes. It's insane to demand massive redeployment of
DNS servers for the sake of a useless protocol modification.

Mark.Andrews@isc.org writes:
> you need to write up a draft

_I_ don't need to write anything. I am not the one trying to change the
requirements in RFC 1034. My software follows the spec.

_Your_ company is trying to impose requirements that aren't in RFC 1034.
You are claiming that most DNS server installations on the Internet have
to be changed. You are demanding that we tolerate configurations that
violate RFC 1034.

Even worse, instead of honestly proposing this protocol change, you are
trying to sneak it past us as part of an ``AXFR clarification''; and
someone who has been paid for BIND work is abusing his position as WG
chair by fraudulently claiming ``consensus.'' This is a sham.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Thu Feb 20 01:21:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20859;
	Thu, 20 Feb 2003 01:21:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lk5I-0001Xy-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 01:21:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lk46-0001X7-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 01:20:14 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20765;
	Thu, 20 Feb 2003 01:11:35 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1K6Ev4U007655;
	Thu, 20 Feb 2003 17:14:57 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302200614.h1K6Ev4U007655@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify breaking RFC 1034 
In-reply-to: Your message of "20 Feb 2003 03:41:48 -0000."
             <20030220034148.14684.qmail@cr.yp.to> 
Date: Thu, 20 Feb 2003 17:14:57 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Here's a chart summarizing the situation:
> 
>    Timing of         |Useful in|RFC 1034 |BIND 8 |BIND 9 |tinydns
>    data change       |practice |compliant|support|support|support
>    ------------------+---------+---------+-------+-------+-------
>    Synchronized      |Yes      |Yes      |No     |No     |Yes
>    Semi-synchronized |Yes      |No       |Yes    |Yes    |Yes
>    Unsynchronized    |No       |No       |No     |Yes    |No

	This is not a accurate summary.
 
> The BIND company observes that
> 
>    * synchronized changes are hard to do with BIND, even though they're
>      required by RFC 1034; and

	RFC 1034 requires the *administators* to keep the glue in sync.

Section 4.2.2. Administrative considerations

As the last installation step, the delegation NS RRs and glue RRs
necessary to make the delegation effective should be added to the parent
zone.  The administrators of both zones should insure that the NS and
glue RRs which mark both sides of the cut are consistent and remain so.

	This is a administrative action.

	If you can automate administrative actions well and good.  Using
	a single file for all your PRIMARY zones is actually a useful
	way to partially achieve this.  It will keep all PRIMARY zones
	on the server in sync.

	If you wish you can copy the contents of a SECONDARY into a 
	PRIMARY provided you also change the SERIAL of the PRIMARY to
	reflect the change.  I wouldn't encorage this as a default
	action however.

	However changing the contents of SECONDARY zones is not allowed.
	That action needs to be performed through the PRIMARY server for
	the zone.  UPDATE could be used to facilitate this.  Again I would
	not encourage this as a default action.

	A server ceases to be a SECONDARY if it changes the zones contents.

>    * unsynchronized changes can fail miserably with BIND 8 et al., which
>      account for the majority of DNS servers.

	Which is why we fixed our server.
 
> The obvious solution is semi-synchronized changes, which work with the
> entire installed base. I wouldn't object to modifying RFC 1034 to allow
> semi-synchronized changes.

	You have to be kidding.  Even if we were to go down that
	path (which I don't believe we should) it still leaves
	servers with the underlying problem in that they are not
	serving the zone contents as entered.
 
> (To repeat the relevant definitions: A synchronized change happens at
> the same time in all the parent servers and all the child servers. A
> semi-synchronized change happens in the parent zone---specifically, the
> parent serial is changed---after it happens in all the child servers.)
> 
> I certainly _do_ object to allowing unsynchronized changes. They don't
> work correctly with the installed base, and they have no advantages over
> semi-synchronized changes. It's insane to demand massive redeployment of
> DNS servers for the sake of a useless protocol modification.

	Nobody is demanding a massive redeployment.  None of the changes
	require a massive redeployment.
 
	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Thu Feb 20 04:03:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04647;
	Thu, 20 Feb 2003 04:03:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lma8-0005G1-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 04:01:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lma3-0005FX-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 04:01:23 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04530
	for <ietf@ietf.org>; Thu, 20 Feb 2003 03:52:44 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2CB7262579; Thu, 20 Feb 2003 09:56:34 +0100 (CET)
Date: Thu, 20 Feb 2003 09:56:34 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "D. J. Bernstein" <djb@cr.yp.to>, ietf@ietf.org
Subject: Warning about the use of abusive language
Message-ID: <809960000.1045731394@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20030220000752.38144.qmail@cr.yp.to>
References: <20030219190124.8908.qmail@cr.yp.to>
 <200302192321.h1JNL94U006491@drugs.dv.isc.org>
 <20030220000752.38144.qmail@cr.yp.to>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mr. Bernstein,

--On torsdag, februar 20, 2003 00:07:52 +0000 "D. J. Bernstein" 
<djb@cr.yp.to> wrote:

> What we have here is much worse: a thoroughly dishonest attempt to slip
> the latter modification past us as part of an ``AXFR clarification.''
> Anyone with a shred of integrity should be opposing this fraud.

The charter for the IETF list (RFC 3005, also visible at 
http://www.ietf.org/maillist.html) includes the sentence

>  Inappropriate postings include:
>
>    - Unsolicited bulk e-mail
>    - Discussion of subjects unrelated to IETF policy, meetings,
>      activities, or technical concerns
>    - Unprofessional commentary, regardless of the general subject
>    - Announcements of conferences, events, or activities that are not
>      sponsored or endorsed by the Internet Society or IETF.
>
>   The IETF Chair, the IETF Executive Director, or a sergeant-at-arms
>   appointed by the Chair is empowered to restrict posting by a person,
>   or of a thread, when the content is inappropriate and represents a
>   pattern of abuse.

Accusations of "dishonesty" and "fraud" in a technical discussion are 
normally considered "unprofessional".

I would also want to direct your attention to RFC 3184, "IETF Guidelines 
for Conduct", which states, among other things:

>   2. IETF participants develop and test ideas impartially, without
>      finding fault with the colleague proposing the idea.
>
>      We dispute ideas by using reasoned argument, rather than through
>      intimidation or ad hominem attack.  Or, said in a somewhat more
>      IETF-like way:
>
>            "Reduce the heat and increase the light"

Note to list: The normal procedure when dealing with unprofessional conduct 
on mailing lists includes a private warning. But since mr. Bernstein has 
chosen not to accept mail from me without asking me to engage in some 
arcane ritual of admission, I have chosen to skip this step in this case.

                        Harald Alvestrand





From owner-ietf@ietf.org  Thu Feb 20 04:19:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05031;
	Thu, 20 Feb 2003 04:19:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lmuW-0005zi-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 04:22:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lmuP-0005zI-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 04:22:25 -0500
Received: from dot-god.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04917
	for <ietf@ietf.org>; Thu, 20 Feb 2003 04:13:46 -0500 (EST)
Received: from localhost (baptista@localhost)
	by dot-god.com (8.11.4/8.11.4) with ESMTP id h1K9IOn22944;
	Thu, 20 Feb 2003 04:18:25 -0500
Date: Thu, 20 Feb 2003 04:18:24 -0500 (EST)
From: Joe Baptista <baptista@dot-god.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: "D. J. Bernstein" <djb@cr.yp.to>, <ietf@ietf.org>
Subject: Re: Warning about the use of abusive language
In-Reply-To: <809960000.1045731394@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.LNX.4.33.0302200413420.30772-100000@dot-god.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Thu, 20 Feb 2003, Harald Tveit Alvestrand wrote:

> Accusations of "dishonesty" and "fraud" in a technical discussion are
> normally considered "unprofessional".

Harald - I must agree with the views expressed by Dr. Bernstein.  As you
know Harald I have had the pleasure of watching the i$ociety these past 10
years and the facts clearly show many members of the same use dishonesty
and fraud as their currency of choice.

> >   2. IETF participants develop and test ideas impartially, without
> >      finding fault with the colleague proposing the idea.
> >
> >      We dispute ideas by using reasoned argument, rather than through
> >      intimidation or ad hominem attack.  Or, said in a somewhat more
> >      IETF-like way:

yes - thats one thing thats nice about the ietf.  at least when it works.

love and kisses
joe baptista

Joe Baptista - only at www.baptista.god

          .film domain registration available at http://www.register.film
             another inclusive namespace Top Level Domain





From owner-ietf@ietf.org  Thu Feb 20 09:09:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14877;
	Thu, 20 Feb 2003 09:09:45 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lrOR-0006uy-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 09:09:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lrLa-0006aG-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 09:06:46 -0500
Received: from net.cc.swin.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14610
	for <ietf@ietf.org>; Thu, 20 Feb 2003 08:58:03 -0500 (EST)
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by net.cc.swin.edu.au (8.9.3/8.9.3) with ESMTP id BAA32540;
	Fri, 21 Feb 2003 01:01:51 +1100 (AEDT)
Message-ID: <3E54DFCF.61CEA099@swin.edu.au>
Date: Fri, 21 Feb 2003 01:01:51 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Warning about the use of abusive language
References: <20030219190124.8908.qmail@cr.yp.to>
	 <200302192321.h1JNL94U006491@drugs.dv.isc.org>
	 <20030220000752.38144.qmail@cr.yp.to> <809960000.1045731394@askvoll.hjemme.alvestrand.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Harald Tveit Alvestrand wrote:
	[..]
> Accusations of "dishonesty" and "fraud" in a technical discussion are
> normally considered "unprofessional".

I'm finding Bernstein's commentary to be robust and colorful (and at times
obtuse, for I'm not a DNS weenie and the relevant details usually elude me).
But not even beginning to get as close to 'unprofessional' as I've seen
on IETF mailing lists over the years.

"Be liberal in what you accept" seems a good philosophy for reading this
list...

cheers,
gja
-- 
Grenville Armitage
http://caia.swin.edu.au



From owner-ietf@ietf.org  Thu Feb 20 13:22:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24136;
	Thu, 20 Feb 2003 13:22:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lvK8-0001x7-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 13:21:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lvJW-0001uX-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 13:20:54 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA23792
	for <ietf@ietf.org>; Thu, 20 Feb 2003 13:12:08 -0500 (EST)
Received: (qmail 26323 invoked by uid 1016); 20 Feb 2003 18:16:26 -0000
Date: 20 Feb 2003 18:16:26 -0000
Message-ID: <20030220181626.26322.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034
References: <20030220034148.14684.qmail@cr.yp.to> <200302200614.h1K6Ev4U007655@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Andrews admits that his configuration violates RFC 1034 section 4.2.2.
He also agrees that DNS servers are allowed to discard the inconsistent
parts of his configuration. (BIND 9 doesn't; djbdns does; BIND 8 does to
some extent.)

However, because the _title_ of section 4.2.2 is ``Administrative
considerations,'' Andrews concludes that DNS servers aren't allowed to
discard the inconsistent parts of his configuration _if_ they obtained
data for the parent zone through AXFR rather than directly from an
``administrator.''

It would be easy to shred the details of that argument. I could point
out again that the configuration also violates section 4.2.1; the title
of section 4.2.1 is ``Technical considerations''; no ``administrators''
here. There are many other obvious mistakes in what Andrews says.

But there's a much larger problem here. Look at the overall structure of
Andrews's argument:

   (1) Observation: This configuration, which is prohibited by RFC 1034,
       doesn't work correctly with 77% of the installed base.

   (2) Insane conclusion: 77% of the installed base is broken! We have
       to change all of it to make this configuration work correctly!
       Let's ignore all the objections, and declare the software used
       for most of the Internet's DNS servers to be non-compliant!

Anyone who cares about interoperability will draw a very different
conclusion:

   (3) Sane conclusion: The configuration is broken. Stop using it.

Andrews is trying to shift blame from the broken configuration to the
installed base. He's fighting against both RFC 1034 and the real world;
that's why he's resorted almost entirely to religious arguments about
proper implementation techniques for servers.

There is one spot where Andrews returns to reality. He points out that
his software (unlike mine) has never supported the synchronization
required by RFC 1034. Obeying RFC 1034 would mean, among other things,
changing all the BIND installations, which would be very difficult.

Does this mean that we need the broken configurations? No! There's a
middle ground between the synchronized configurations required by RFC
1034 and the broken configurations: namely, semi-synchronized
configurations (parent serial changing after all the child servers have
changed), which work with the entire installed base. RFC 1034 can be
modified to allow semi-synchronized configurations.

Mark.Andrews@isc.org writes:
> Even if we were to go down that path (which I don't believe we should)

Let me get this straight, Mark. You're screaming that the RFC 1034
requirement is too restrictive---because it requires synchronization
that your software can't handle---but you don't believe that it should
be changed to allow configurations that work with all existing software?

You know, Mark, this discussion would have been a lot easier if your
company had started by making an honest proposal to change the protocol,
instead of trying to sneak changes past us as ``clarifications.''

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Thu Feb 20 15:17:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28110;
	Thu, 20 Feb 2003 15:17:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lx4W-0007hb-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 15:13:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lx3r-0007ew-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 15:12:51 -0500
Received: from astro.cs.utk.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27729;
	Thu, 20 Feb 2003 15:04:05 -0500 (EST)
Received: from astro.cs.utk.edu (localhost [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with SMTP id h1KK7qA11319;
        Thu, 20 Feb 2003 15:07:53 -0500 (EST)
Date: Thu, 20 Feb 2003 15:07:52 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: moore@cs.utk.edu, ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
Message-Id: <20030220150752.357be0cc.moore@cs.utk.edu>
In-Reply-To: <20030215033141.82623.qmail@cr.yp.to>
References: <20030214103228.71052.qmail@cr.yp.to>
	<200302101659.LAA15654@ietf.org>
	<10697.1045222702@munnari.OZ.AU>
	<20030215033141.82623.qmail@cr.yp.to>
X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> RFC 2119, section 6: ``Imperatives of the type defined in this memo
> must be used with care and sparingly.  In particular, they MUST only
> be used where it is actually required for interoperation or to limit
> behavior which has potential for causing harm (e.g., limiting
> retransmisssions) For example, they must not be used to try to impose
> a particular method on implementors where the method is not required
> for interoperability.''

fwiw, this only applies to documents that cite RFC 2119 for
definitions of those terms. other documents have used other
definitions.





From owner-ietf@ietf.org  Thu Feb 20 16:10:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29588;
	Thu, 20 Feb 2003 16:10:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lxye-0002Ja-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 16:11:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lxy2-0002Gp-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 16:10:54 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA29399
	for <ietf@ietf.org>; Thu, 20 Feb 2003 16:02:06 -0500 (EST)
Received: (qmail 40639 invoked by uid 1016); 20 Feb 2003 21:06:23 -0000
Date: 20 Feb 2003 21:06:23 -0000
Message-ID: <20030220210623.40638.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030214103228.71052.qmail@cr.yp.to> <200302101659.LAA15654@ietf.org> <10697.1045222702@munnari.OZ.AU> <20030215033141.82623.qmail@cr.yp.to> <20030220150752.357be0cc.moore@cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Keith Moore writes:
  [ RFC 2119 section 6 ]
> only applies to documents that cite RFC 2119 for definitions of those terms.

That's exactly what axfr-clarify does in section 1: ``The key words
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC 2119].''

The author will, presumably, try to weasel out of RFC 2119 section 6 by
dropping the reference to RFC 2119. Why is this tolerated? Why would any
legitimate standards organization _want_ to violate the basic principles
stated in RFC 2119? The IETF shouldn't be sticking its nose into private
implementation decisions that don't cause interoperability problems.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Thu Feb 20 17:19:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01742;
	Thu, 20 Feb 2003 17:19:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lz2R-0005dH-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 17:19:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lywX-0005Pu-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 17:13:25 -0500
Received: from halt-in.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01419;
	Thu, 20 Feb 2003 17:04:37 -0500 (EST)
Received: from cisco.com (171.70.144.164)
  by halt-in.cisco.com with ESMTP; 20 Feb 2003 14:08:33 -0800
Received: from cisco.com (dhcp-171-71-119-196.cisco.com [171.71.119.196]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA02611; Thu, 20 Feb 2003 14:08:27 -0800 (PST)
Message-ID: <3E5551DB.2060808@cisco.com>
Date: Thu, 20 Feb 2003 14:08:27 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "D. J. Bernstein" <djb@cr.yp.to>
CC: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030214103228.71052.qmail@cr.yp.to> <200302101659.LAA15654@ietf.org> <10697.1045222702@munnari.OZ.AU> <20030215033141.82623.qmail@cr.yp.to> <20030220150752.357be0cc.moore@cs.utk.edu> <20030220210623.40638.qmail@cr.yp.to>
In-Reply-To: <20030220210623.40638.qmail@cr.yp.to>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

D. J. Bernstein wrote:
> The IETF shouldn't be sticking its nose into private
> implementation decisions that don't cause interoperability problems.

But Rob Elz made a clear point in seemingly the only message you 
*didn't* respond to that your implementation could cause 
interoperability problems by potentially allowing for different contents 
of the same zone with the same serial number.  I won't regurgitate the 
rest of his message, but it's in the archives.

If he's right (and it seems to me that he is), that's an indication for 
either a standards clarification or a bug fix to your code, and maybe 
both (indicated, IMHO).

Eliot




From owner-ietf@ietf.org  Thu Feb 20 17:36:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02268;
	Thu, 20 Feb 2003 17:36:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18lzMm-0007qu-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 17:40:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lzLm-0007mg-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 17:39:30 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02129;
	Thu, 20 Feb 2003 17:30:39 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1KMXO4U009264;
	Fri, 21 Feb 2003 09:33:26 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302202233.h1KMXO4U009264@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Thu, 20 Feb 2003 11:32:38 CDT."
             <Pine.LNX.4.44.0302201039370.11133-100000@commander.av8.net> 
Date: Fri, 21 Feb 2003 09:33:24 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> > > > > The IXFR client must simply make the changes (again, by some
> > > > > implementation dependent, administrator maintained method) to the zon
> e by
> > > > > deleting RRs and adding RR's in each sequence. The original version o
> f th
> > > e
> > > > > zone might have been obtained by FTP (or quantum interference, or the
> > > > > psychic network) for all we know.
> > > >
> > > > 	Well the problem is that you have to get the *original* version
> ,
> > > > 	not a corrupted version.  AXFR implementations are not returnin
> g
> > > > 	the data originally entered.
> > >
> > > They sure have been.
> >
> > 	Not always.
> 
> You haven't shown any proof of that.  The "proof" you showed, was the
> result of a misconfiguration.

	No.  It is the result of operational reality.  Whenever you
	have a parent and child zones under different administrative
	controls it is impossible to change both zones simultaniously.
	It is also impossible using AXFR or any other mechanism
	which transfers *individual* zones to transfer them to a
	secondary and guarantee that they will arrive simultaniously.

	Having parent and child zone under different administrative control
	is the norm not the execption.

> > > If the zones are inconsistent through administrative mistake, then it
> > > won't matter what the IXFR does.
> >
> > 	Who said anything administrative mistakes?  The content is being
> > 	unilaterally changed by the servers.
> 
> It is reasonable and necessary to merge in glue. When you misconfigure the
> glue, strange things may happen. That is all that you have shown.  I'm
> sure that many software programs will exhibit even stranger behavior, and
> may even fail to operate as a result of misconfiguration.

	No.  It is neither reasonable nor necessary.  Any temporary
	inconsistancies will be corrected when all the zone transfers
	complete.  By changing the zones contents you create
	situations where these temporary inconsistancies won't be
	corrected.  When handing out non axfr/ixfr responses you
	use the best source of data you have.

	Nothing in RFC 1033 / 1034 / 1035 says that a server is permitted
	to alter the content of a zone.  The responability for maintaining
	consistancy between zones is a administrative function.
 
> > > Strange, that was my reaction, too. I'm just trying to be polite.  77%
> > > work just fine. We don't want to break 77% of the servers out there.
> >
> > 	You really think that it will break those servers?  LOL.
> 
> They will not be compliant, and thus will need to be changed. Thus, they
> would be broken by definition of not being compliant.

	So.  Just because they will not be compliant doesn't mean
	that that they need to be replaced immediately.  That
	non-compliance doesn't hurt most of them.  For those where
	it does have a negative impact it will mean that they should
	be able to request a fix from their vendor.

> Your failure to comprehend the consequences of the changes does not lessen
> the effect.  We now agree that these changes aren't necessary to support
> IXFR. You were part of the bad engineering that led to the unnecessary
> creation of these changes in Bind 9.  You were also part of the bad
> decision making that led to the distribution of these changes to Bind 9
> users prior to standardization, and quite possibly you were part of the
> bad decision making that resulted in publishing a book on the subject,
> prior to acceptance of your modifications to standards. In short, you have
> shown bad judgement.

	I never said that they we not necessary for IXFR.  I said that
	that your descripition of how to generate the differences was
	irrelevent to this discussion.

	It was bad engineering to merge the data sets together in the
	first place.  It was not required by RFC 1033/ 1034 / 1035.
	It had negative consequences.  It was good engineering to
	correct this.  It was also good engineering to report a
	common error to the community so that other vendors could
	fix their mistakes.
 
	Good engineers learn from their mistakes and try hard not
	to repeat them.  They also learn from the mistakes of others.
	That's why bridge designs are wind tunnel tested these days.

> Trying to "belittle" the effects with the "LOL", as opposed to offering
> anything substantive, simply suggests that you have no appreciation of the
> seriousness of the changes.  Perhaps you should take this more seriously.

	I'm quite aware of what the change requires.  I'm also aware
	that most of the nameserver are used in situations where
	the zone contents is already preserved because they are not
	serving zones with parent / child relationships.

	Anyone saying that all the nameservers need to be replaced
	immediately is spreading FUD.  LOL the the correct reponse
	to FUD.
 
	Using a server that perserves zone contents under all
	conditions doesn't break anything.

> > > > > Essentially, you are putting more (unnecessary) constraints on
> > > > > implementations, and thus on the administrators, who are supposed to 
> be
> > > > > pretty free to define the zone boundaries.  Of course, the specifics 
> of a
> > > n
> > > > > implementation puts some constraints on the adminstrator, but the
> > > > > administrator can choose a different implementation more to her likin
> g.
> > > >
> > > > 	The constaint was already there and it is necessary for reliabl
> e
> > > > 	operation of the DNS.
> > >
> > > No, you ware not being honest about the contents of the Draft. See my las
> t
> > > message to Andreas.
> >
> > 	The abstract say:
> >
> > 				    This memo clarifies, updates, and
> >    adds missing detail to the original AXFR protocol specification in
> >    RFC1034.
> >
> > 	I fail to see how the contents can be deemed misleading when
> > 	it states up front what it does.  Woops we missed warning you
> > 	up front that it contains a warning.
> 
> I've no doubt that you fail to see it. We seem to be focusing a lot on
> your failures. I have to question whether someone who went to MIT could
> really fail so often. Perhaps it has changes since I was there. Or perhaps
> you aren't really taking this very seriously. Let me explain it:
> 
> 1) It doesn't say that it adds a completely new, incompatible zone
> transfer protocol.  New protocols should be made through a different
> process, which includes experimentation. I'm not against experimenting
> with a new protocol. Indeed, I think this idea has some merit. However, it
> can't be "end-run standardized" by a "clarification". There is a process.

	It isn't new.  All it is saying is that the contents tramitted
	out MUST be that transmitted in.  This occurs most of the time
	already.  Note BIND is not the only implementation that does
	this.  We have already had reports of 3 other implementations
	doing this.  Even the implementations that don't guarentee the
	contents do this most of the time.  It has no negative effects.

> 2) It doesn't say that it changes AXFR with respect to SIG

	It doesn't change anything wrt to SIG.  Go read RFC 2535 which
	also says that SIG records in the answer section are part of the
	zone contents and don't need special processing.
 
> 3) It doesn't say that it changes the status of other RFC's (RFC 2845, and
> possibly others.) without going through the appropriate standards process.

	It doen't change the status of RFC 2845.
 
> 4) It doesn't say that it changes the definition of zone data to be
> public. Zone data is absolutely not "public by definition". It could very
> well be useful to tag certain RRs as non-public, and exclude them from
> zone transfers to public servers. This "clarification" precludes that.
> This is really 2 changes.

	Nowhere in RFC 1033 / 1034 / 1035 does it say that zone transfers
	are restricted to secondaries.  Nowhere in RFC 1033 / 1034 / 1035
	does it say that you should restrict zone tranfers.
 
	There is a REFUSED rcode so the possibility of refusing a zone
	transfer is allowed for but the conditions underwhich this will
	be done are not specified.  This draft does not change this.

> 5) It doesn't say that it changes the security constraints on a zone
> transfer to be limited to deny or accept only.

	Effective it does.  If you transmit the zone then you MUST
	transmit its full contents unmodified (accept).  It also
	says that you are allowed to refuse zone transfers (deny).

> The list is longer, but that should be enough.
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Thu Feb 20 19:20:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04566;
	Thu, 20 Feb 2003 19:20:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m0wW-00047Y-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 19:21:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m0uY-000417-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 19:19:30 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04242;
	Thu, 20 Feb 2003 19:10:38 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1L0EH4U009904;
	Fri, 21 Feb 2003 11:14:18 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302210014.h1L0EH4U009904@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify breaking RFC 1034 
In-reply-to: Your message of "20 Feb 2003 18:16:26 -0000."
             <20030220181626.26322.qmail@cr.yp.to> 
Date: Fri, 21 Feb 2003 11:14:17 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Andrews admits that his configuration violates RFC 1034 section 4.2.2.

	It's a necessary and unavoidable reality to temporarily
	violate it.

	The only way to meet this all the times and at all levels
	of the DNS is to have the all the zones administered on a
	single machine *and* to have a multizone transfer protocol.

	Lets go back to HOSTS.TXT, that meets this criteria.

> He also agrees that DNS servers are allowed to discard the inconsistent
> parts of his configuration. (BIND 9 doesn't; djbdns does; BIND 8 does to
> some extent.)

	No.  I agree that server can be configured to correct PRIMARY
	zones if they detect a inconsistancy and if they do so they
	have to update the serial number.
 
> However, because the _title_ of section 4.2.2 is ``Administrative
> considerations,'' Andrews concludes that DNS servers aren't allowed to
> discard the inconsistent parts of his configuration _if_ they obtained
> data for the parent zone through AXFR rather than directly from an
> ``administrator.''

	It is not the servers job to correct inconsistancies in SECONDARY
	zones.

	RFC 1034 states that a ACURATE copy of the zone is ESSENTIAL.

					"The stream of messages allows
the secondary to construct a copy of the zone.  Because accuracy is
essential, TCP or some other reliable protocol must be used for AXFR
requests."
 
	A modified zone is NOT a ACURATE copy.  It's not even
	a copy.  It is a derived work.

	BIND 4 and BIND 8 violate this section of RFC 1034.
	BIND 9 does not.

> It would be easy to shred the details of that argument. I could point
> out again that the configuration also violates section 4.2.1; the title
> of section 4.2.1 is ``Technical considerations''; no ``administrators''
> here. There are many other obvious mistakes in what Andrews says.
>
> But there's a much larger problem here. Look at the overall structure of
> Andrews's argument:
> 
>    (1) Observation: This configuration, which is prohibited by RFC 1034,
>        doesn't work correctly with 77% of the installed base.
> 
>    (2) Insane conclusion: 77% of the installed base is broken! We have
>        to change all of it to make this configuration work correctly!
>        Let's ignore all the objections, and declare the software used
>        for most of the Internet's DNS servers to be non-compliant!

	The installed base is broken.  It doesn't matter if it is 1%,
	77% or 100%.
 
> Anyone who cares about interoperability will draw a very different
> conclusion:
> 
>    (3) Sane conclusion: The configuration is broken. Stop using it.

	No.  The sane conclusion is to deal with physical and
	administative realities.  To stop fighting the speed of
	light and correct the implementations.
 
> Andrews is trying to shift blame from the broken configuration to the
> installed base. He's fighting against both RFC 1034 and the real world;
> that's why he's resorted almost entirely to religious arguments about
> proper implementation techniques for servers.
> 
> There is one spot where Andrews returns to reality. He points out that
> his software (unlike mine) has never supported the synchronization
> required by RFC 1034. Obeying RFC 1034 would mean, among other things,
> changing all the BIND installations, which would be very difficult.
> 
> Does this mean that we need the broken configurations? No! There's a
> middle ground between the synchronized configurations required by RFC
> 1034 and the broken configurations: namely, semi-synchronized
> configurations (parent serial changing after all the child servers have
> changed), which work with the entire installed base. RFC 1034 can be
> modified to allow semi-synchronized configurations.

	It is good to see that you agree that Section 4.2.2 cannot
	be met all the time.  It is good to see that you agree that
	enforcing agreement between zones causes problem.  The
	logical conclusion is to stop enforcing agreement between
	zones where it causes problems.

> Mark.Andrews@isc.org writes:
> > Even if we were to go down that path (which I don't believe we should)
> 
> Let me get this straight, Mark. You're screaming that the RFC 1034
> requirement is too restrictive---because it requires synchronization
> that your software can't handle---but you don't believe that it should
> be changed to allow configurations that work with all existing software?
>
> You know, Mark, this discussion would have been a lot easier if your
> company had started by making an honest proposal to change the protocol,
> instead of trying to sneak changes past us as ``clarifications.''
> 
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Thu Feb 20 23:04:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08722;
	Thu, 20 Feb 2003 23:04:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m4QI-0007VC-00
	for ietf-list@ran.ietf.org; Thu, 20 Feb 2003 23:04:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m4Ps-0007TT-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 23:04:04 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA08537;
	Thu, 20 Feb 2003 22:55:08 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1L3vr4U010801;
	Fri, 21 Feb 2003 14:57:55 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302210357.h1L3vr4U010801@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Thu, 20 Feb 2003 21:07:49 CDT."
             <Pine.LNX.4.44.0302201959400.13516-100000@commander.av8.net> 
Date: Fri, 21 Feb 2003 14:57:53 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:
> 
> > > You haven't shown any proof of that.  The "proof" you showed, was the
> > > result of a misconfiguration.
> >
> > 	No.  It is the result of operational reality.  Whenever you
> > 	have a parent and child zones under different administrative
> > 	controls it is impossible to change both zones simultaniously.
> > 	It is also impossible using AXFR or any other mechanism
> > 	which transfers *individual* zones to transfer them to a
> > 	secondary and guarantee that they will arrive simultaniously.
> >
> > 	Having parent and child zone under different administrative control
> > 	is the norm not the execption.
> 
> Actually, a parent always has some control over the child. It exercises
> this control through the glue records.  When the glue records are in the
> child zone, they need to be merged.

	Which is it.  Does the parent control the contents of its zone
	or does the child?

> If a zone transfer happens while they
> are inconsistent, it is possible for some strange results to happen.
> Ordinarilly, zone transfers don't happen when they are inconsistent, since
> the inconsistency is usually short.

	It doesn't matter if they normally happen while they are
	consistant.  You have to get correct behaviour while they
	are inconsistant.  Changing zone content on SECONDARY servers
	is not correct behaviour.
 
> Any zone transfers made during the inconsistent window are corrected so
> long as the child zone is updated with correct information after the
> parent is updated.

	This is a incorrect statement.
 
> Frequently the parent and child zone are under different administrative
> control, and are frequently on different servers. In such a case, the
> contents of the parent zone aren't merged with the child in the child's
> server, and no evidence of the inconsistency is seen through zone
> transfers. However, the inconsistency still exists and may still be
> visible by resolvers and nameservers that lookup the glue records.

	Nobody is claiming that inconsistancies don't occur all the
	time.  What we are claiming is that those inconsistancies
	need to be preserved in SECONDARY servers for the correct
	operation of the DNS.  That they can only be corrected by
	modifying the PRIMARY source of the zones.
 
> You have obtained no benefits by these constraints.

	There are clear benefits in preserving zone contents on
	SECONDARY servers.
 
> > > > > If the zones are inconsistent through administrative mistake, then it
> > > > > won't matter what the IXFR does.
> > > >
> > > > 	Who said anything administrative mistakes?  The content is bein
> g
> > > > 	unilaterally changed by the servers.
> > >
> > > It is reasonable and necessary to merge in glue. When you misconfigure th
> e
> > > glue, strange things may happen. That is all that you have shown.  I'm
> > > sure that many software programs will exhibit even stranger behavior, and
> > > may even fail to operate as a result of misconfiguration.
> >
> > 	No.  It is neither reasonable nor necessary.  Any temporary
> > 	inconsistancies will be corrected when all the zone transfers
> > 	complete.  By changing the zones contents you create
> > 	situations where these temporary inconsistancies won't be
> > 	corrected.  When handing out non axfr/ixfr responses you
> > 	use the best source of data you have.
> 
> It is necessary, since the parent has glue records in the child zone.
> The parent therefore has (always) a part of the child zone. If that server
> also loads the child zone (or perhaps generates part of it dynamically),
> it quite reasonable to merge the records as though the zone includes
> multiple files, which in theory, it does.

	No it isn't.  Changes need to come from the PRIMARY source not
	from intermediate sources.
 
> The child zone contents will only be correct when the administrators of
> both zones agree on the contents of the glue records, and update their
> parts of the child zone accordingly. It will not be correct until then,
> regardless of how many zone transfers take place.

	Which is what I've been saying all along.  It doesn't require
	a server to "correct" the content at a intermediate point.  Such
	"corrections" actually cause problems.
 
> > 	Nothing in RFC 1033 / 1034 / 1035 says that a server is permitted
> > 	to alter the content of a zone.  The responability for maintaining
> > 	consistancy between zones is a administrative function.
> 
> This is a loaded statement. The part of the server NOT involved in
> responding to queries and zone transfers is part of the administrative
> function. So, as part of that administrative function, it has to be able
> to modify the RR and zones accordingly.  Your proposed changes exclude a
> huge part of the potential for intelligence in name servers. And do so
> with no benefits.

	The benefits are correct operation of the DNS regardless of the
	propogation timings involved.  If servers don't modify slave zone
	content then which the master servers are brought into sync all
	the servers will be brought into sync.

	This is not guarenteed if the zone content is modified by a
	secondary server.
 
> > > > > Strange, that was my reaction, too. I'm just trying to be polite.  77
> %
> > > > > work just fine. We don't want to break 77% of the servers out there.
> > > >
> > > > 	You really think that it will break those servers?  LOL.
> > >
> > > They will not be compliant, and thus will need to be changed. Thus, they
> > > would be broken by definition of not being compliant.
> >
> > 	So.  Just because they will not be compliant doesn't mean
> > 	that that they need to be replaced immediately.  That
> > 	non-compliance doesn't hurt most of them.  For those where
> > 	it does have a negative impact it will mean that they should
> > 	be able to request a fix from their vendor.
> 
> You seem to make a case that in general, non-compliance doesn't hurt
> anything. This is false, for both technical and commercial reasons.
> Technically, it hurts interoperability, which has some many obvious harms
> I won't go into them. Commercially, implementations make and advertise
> compatibility and standards compliance claims. This retroactively makes
> those claims false, which harms the business and reputation of those other
> vendors.

	They will be harmed much more if they don't correct a common
	error now that it has been pointed out.

	The claims were made in good faith and will be accepted as
	such.
	
> 77% will need a fix from the vendor, if we were to accept these changes.
> 
> The vendor that made false claims of compatibility and standards
> compliance is Bind 9. It should suffer the commercial damage to its
> business and reputation, as a result.

	BIND 9 conforms to RFC 1034.  Nothing in RFC 1034 says to
	merge zone content.  If fact 1034 says that this a administrative
	responsability.
 
> > > Your failure to comprehend the consequences of the changes does not lesse
> n
> > > the effect.  We now agree that these changes aren't necessary to support
> > > IXFR. You were part of the bad engineering that led to the unnecessary
> > > creation of these changes in Bind 9.  You were also part of the bad
> > > decision making that led to the distribution of these changes to Bind 9
> > > users prior to standardization, and quite possibly you were part of the
> > > bad decision making that resulted in publishing a book on the subject,
> > > prior to acceptance of your modifications to standards. In short, you hav
> e
> > > shown bad judgement.
> >
> > 	I never said that they we not necessary for IXFR.  I said that
> > 	that your descripition of how to generate the differences was
> > 	irrelevent to this discussion.
> 
> Ok, you are half way there. They are irrelevant because IXFR is
> irrelevant. These changes are not necessary to IXFR, as I explained that
> IXFR can work with the current AXFR, or even without AXFR.

	IXFR cannot work through SECONDARY servers that change zone
	content regardless of whether the content was learnt via
	AXFR or IXFR.

> > 	It was bad engineering to merge the data sets together in the
> > 	first place.  It was not required by RFC 1033/ 1034 / 1035.
> > 	It had negative consequences.  It was good engineering to
> > 	correct this.  It was also good engineering to report a
> > 	common error to the community so that other vendors could
> > 	fix their mistakes.
> 
> Actually, since the parent has the glue in the child zone, it has part of
> the child zone as well as the master zone.  Merging them together is not
> prohibited, and in the case where child and parent have the same
> adminstrator, as might be the case where most of the child is simply
> automatically generated by the nameserver, can make things much easier.
> 
> Your constraints preclude this unnecessarilly.

	The constraint in on the SECONDARY server.
 
> Since I can think of cases where it is useful to merge records together,
> it is bad engineering to remove that flexibility and obtain no benefits in
> return.
> 
> > > Trying to "belittle" the effects with the "LOL", as opposed to offering
> > > anything substantive, simply suggests that you have no appreciation of th
> e
> > > seriousness of the changes.  Perhaps you should take this more seriously.
> >
> > 	I'm quite aware of what the change requires.  I'm also aware
> > 	that most of the nameserver are used in situations where
> > 	the zone contents is already preserved because they are not
> > 	serving zones with parent / child relationships.
> 
> Apparently, you aren't even aware that your changes will make all non-bind
> 9 servers non-compliant.  Had you been aware of that, it seems you would
> have brought this proposal forward something like 3 years ago, before
> releasing Bind 9, and before publishing a book on the subject.

	Well you obviously have not been reading.  ISC is not the
	only vendor to come to the same conclusion about preserving
	zone content.  I suspect that they are just bored with
	arguing with you and Dan.
 
> > 	Anyone saying that all the nameservers need to be replaced
> > 	immediately is spreading FUD.  LOL the the correct reponse
> > 	to FUD.
> 
> Making 77% of the servers non-compliant is a fact of your proposed
> changes.  It is another fact, as explained, that non-compliant servers
> will need to be replaced.  Will they suddenly stop working? It depends on
> whether other implementations want to implement a "backwards
> compatibility" mode. If they don't implement this mode, then the answer is
> yes, they will stop working as soon as these updates are deployed by other
> vendors. Of course, this is a bad result.

	Well they havn't stopped working in the last two years that
	this code has been out there.  Nothing in this drafts stops
	a server implementing it taking to any other server.

	There is one backwards compatiblity switch which is only
	requires if you decide to send multiple records in a single
	messages.  A server is not required to send multiple records
	in a single message.

> > 	Using a server that perserves zone contents under all
> > 	conditions doesn't break anything.
> 
> Your constraints break useful services, and offer no value in return.

	What's useful about modifing the contents of a slave zone?  All
	I can see is harm.
 
> > > 1) It doesn't say that it adds a completely new, incompatible zone
> > > transfer protocol.  New protocols should be made through a different
> > > process, which includes experimentation. I'm not against experimenting
> > > with a new protocol. Indeed, I think this idea has some merit. However, i
> t
> > > can't be "end-run standardized" by a "clarification". There is a process.
> >
> > 	It isn't new.  All it is saying is that the contents tramitted
> > 	out MUST be that transmitted in.  This occurs most of the time
> > 	already.  Note BIND is not the only implementation that does
> > 	this.  We have already had reports of 3 other implementations
> > 	doing this.  Even the implementations that don't guarentee the
> > 	contents do this most of the time.  It has no negative effects.
> 
> No, Section 3.1 is a whole new derivative of AXFR. That is new.

	Actually it's always been allowed by RFC 1034.  Just because
	it wasn't implement initially doesn't mean that it was not
	allowed.
 
> > > 2) It doesn't say that it changes AXFR with respect to SIG
> >
> > 	It doesn't change anything wrt to SIG.  Go read RFC 2535 which
> > 	also says that SIG records in the answer section are part of the
> > 	zone contents and don't need special processing.
> 
> Oh. Then section 3.3 can be deleted in entirety without objection.
> 
> > > 3) It doesn't say that it changes the status of other RFC's (RFC 2845, an
> d
> > > possibly others.) without going through the appropriate standards process
> .
> >
> > 	It doen't change the status of RFC 2845.
> 
> The IEFT index indicates that RFC 2845 is "Proposed Standard", with no
> applicability statement that I could find.  This changes it to
> "RECOMMENDED" requirement level.  I think an applicability statement is
> premature until RFC 2845 is moved along, and then by the appropriate
> standards body decision-making process. It is inappropriate to hide
> something like this deep in an irrelevant "clarification".
>
> > > 4) It doesn't say that it changes the definition of zone data to be
> > > public. Zone data is absolutely not "public by definition". It could very
> > > well be useful to tag certain RRs as non-public, and exclude them from
> > > zone transfers to public servers. This "clarification" precludes that.
> > > This is really 2 changes.
> >
> > 	Nowhere in RFC 1033 / 1034 / 1035 does it say that zone transfers
> > 	are restricted to secondaries.  Nowhere in RFC 1033 / 1034 / 1035
> > 	does it say that you should restrict zone tranfers.
> 
> I don't think you understood my statement. I'm talking about the
> definition of zone data. Nowhere does 1034 etc say that zone data is
> public.  It may well have been thought to be public, originally, but since
> I can easily see a useful purpose in withholding some private RRs, there
> isn't any reason to preclude that behavior.

	Does this address your concerns?

   "The zone transfer protocol allows read-only access to the complete
   zone data.  When the data being served to the public it is
   generally acceptable to allow unrestricted access to it via AXFR.
   Sites that wish to avoid disclosing their full zone data MAY
   restrict zone transfer access to authorized slaves."

	If you have part of a zone to which you would normally
	return REFUSED to I suggest that you also return REFUSED
	to AXFR.

	If you want to be able to return partial zones then I suggest
	that a new TYPE be defined so that receipients can know
	that the results will be incomplete.

> Your constraints harm a useful purpose, and provide no benefits.
> > 	There is a REFUSED rcode so the possibility of refusing a zone
> > 	transfer is allowed for but the conditions underwhich this will
> > 	be done are not specified.  This draft does not change this.
> 
> Your modifications put additional and unnecessary restrictions on a zone
> transfer. Again, these restrictions have no useful purpose.

 
> > > 5) It doesn't say that it changes the security constraints on a zone
> > > transfer to be limited to deny or accept only.
> >
> > 	Effective it does.  If you transmit the zone then you MUST
> > 	transmit its full contents unmodified (accept).  It also
> > 	says that you are allowed to refuse zone transfers (deny).
> 
> This was addressed in the previous comments.
> 
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Fri Feb 21 01:42:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10892;
	Fri, 21 Feb 2003 01:42:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m6tC-0004VT-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 01:42:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m6sj-0004Tj-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 01:42:01 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA10729
	for <ietf@ietf.org>; Fri, 21 Feb 2003 01:33:07 -0500 (EST)
Received: (qmail 35915 invoked by uid 1016); 21 Feb 2003 06:37:25 -0000
Date: 21 Feb 2003 06:37:25 -0000
Message-ID: <20030221063725.35914.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification
References: <Pine.LNX.4.44.0302201039370.11133-100000@commander.av8.net> <200302202233.h1KMXO4U009264@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> Whenever you have a parent and child zones under different administrative
> controls it is impossible to change both zones simultaniously.

False.

Set the clocks correctly, and schedule the change on all the servers for
a particular time, using (for example) the tinydns timestamp feature
described in http://cr.yp.to/djbdns/tinydns-data.html. When that time
rolls around, all the servers will change their data simultaneously, as
RFC 1034 requires.

Yes, this is difficult to achieve with BIND, AXFR, etc. But it's easy to
achieve with better software, better replication protocols, etc. You're
making a fool of yourself when you call it ``impossible.''

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 21 02:05:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17917;
	Fri, 21 Feb 2003 02:05:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m7IM-0005lg-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 02:08:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m7Hk-0005jn-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 02:07:52 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11222
	for <ietf@ietf.org>; Fri, 21 Feb 2003 01:59:00 -0500 (EST)
Received: (qmail 41428 invoked by uid 1016); 21 Feb 2003 07:03:17 -0000
Date: 21 Feb 2003 07:03:17 -0000
Message-ID: <20030221070317.41427.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify breaking RFC 1034
References: <20030220181626.26322.qmail@cr.yp.to> <200302210014.h1L0EH4U009904@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
  [ about RFC 1034's database-consistency requirement ]
> The only way to meet this all the times and at all levels
> of the DNS is to have the all the zones administered on a
> single machine *and* to have a multizone transfer protocol.

False; and, more importantly, irrelevant.

RFC 1034 clearly prohibits your broken configurations. You admit this.
It's now obvious to everybody that you're talking about real protocol
changes, not ``clarifications.''

You want to change the protocol. Okay. Make an honest proposal in the
DNSEXT WG, and we'll discuss it. Don't try to slip it past us as part
of an ``AXFR clarification.''

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 21 02:26:18 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21802;
	Fri, 21 Feb 2003 02:26:18 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m7df-0006oc-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 02:30:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m7dZ-0006mh-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 02:30:25 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21746;
	Fri, 21 Feb 2003 02:21:26 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1L7Nr4U011442;
	Fri, 21 Feb 2003 18:23:55 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302210723.h1L7Nr4U011442@drugs.dv.isc.org>
To: Dean Anderson <dean@av8.com>
Cc: Mark_Andrews@isc.org, mw-list-namedroppers@csi.hu,
        Name Droppers <namedroppers@ops.ietf.org>, ietf@ietf.org,
        iesg@ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "Fri, 21 Feb 2003 00:25:56 CDT."
             <Pine.LNX.4.44.0302202333060.13516-100000@commander.av8.net> 
Date: Fri, 21 Feb 2003 18:23:53 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:
> 
> >
> > > On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:
> > >
> > > > > You haven't shown any proof of that.  The "proof" you showed, was the
> > > > > result of a misconfiguration.
> > > >
> > > > 	No.  It is the result of operational reality.  Whenever you
> > > > 	have a parent and child zones under different administrative
> > > > 	controls it is impossible to change both zones simultaniously.
> > > > 	It is also impossible using AXFR or any other mechanism
> > > > 	which transfers *individual* zones to transfer them to a
> > > > 	secondary and guarantee that they will arrive simultaniously.
> > > >
> > > > 	Having parent and child zone under different administrative con
> trol
> > > > 	is the norm not the execption.
> > >
> > > Actually, a parent always has some control over the child. It exercises
> > > this control through the glue records.  When the glue records are in the
> > > child zone, they need to be merged.
> >
> > 	Which is it.  Does the parent control the contents of its zone
> > 	or does the child?
> 
> You seem not to understand the subtlety of the issue. The parent (like
> real parents) ultimately controls the child, but the child (like real
> children) has limited autonomy.

It is a subtle issue.  You can only apply changes to the PRIMARY source
of the data.  Applying changes at any other point has the potential to
cause servers to serve incorrect content.
 
> > > If a zone transfer happens while they
> > > are inconsistent, it is possible for some strange results to happen.
> > > Ordinarilly, zone transfers don't happen when they are inconsistent, sinc
> e
> > > the inconsistency is usually short.
> >
> > 	It doesn't matter if they normally happen while they are
> > 	consistant.  You have to get correct behaviour while they
> > 	are inconsistant.  Changing zone content on SECONDARY servers
> > 	is not correct behaviour.
> 
> Sure it is. Unless you can arrange to conduct both updates simultaneosly.
> While it would be possible to coordinate such changes on the phone,
> relativity could come into play someday.  It has nothing to do with zone
> transfers. Its part of the state of the system. Zone transfers is only one
> way to learn about the state of the system.

Changing the content of zones in SECONDARY servers prevents other SECONARY
servers using the first SECONDARY server learning the correct state of the
system.
 
> > > Any zone transfers made during the inconsistent window are corrected so
> > > long as the child zone is updated with correct information after the
> > > parent is updated.
> >
> > 	This is a incorrect statement.
> 
> Could you elaborate?

	Server A master to parent.
	Server B master to child.
	Server C slave to parent and child.
	Server D slave to parent using C as master.

	All servers with NS RRset N of child zone.

	Server B updates NS RRset to N'.
	Server A updates NS RRset to N'.
	Server C transfers parent from A.
	Server D transfers parent zone from C.
	Server C transfers child zone from B.

	End state with modification (BIND 8/tinydns).
	Server A N', Server B N', Server C N', Server D N.

	End state without modificatin (BIND 9).
	Server A N', Server B N', Server C N', Server D N'.

	You will notice that the last transfer above was the transfer of
	the child zone.
 
	Now lets update the child last.

	Server A updates NS RRset to N'.
	Server B updates NS RRset to N'.
	Server C transfers parent from A.
	Server D transfers parent zone from C.
	Server C transfers child zone from B.
	
	End state with modification (BIND 8/tinydns).
	Server A N', Server B N', Server C N', Server D N.

	End state without modificatin (BIND 9).
	Server A N', Server B N', Server C N', Server D N'.
	
	You will notice that the last transfer above was the transfer of
	the child zone.

	Lets wait for the parent zone to propogate to all servers
	before updating the child zone.

	Server A updates NS RRset to N'.
	Server C transfers parent from A.
	Server D transfers parent zone from C.
	Server B updates NS RRset to N'.
	Server C transfers child zone from B.

	End state with modification (BIND 8/tinydns).
	Server A N', Server B N', Server C N', Server D N.

	End state without modificatin (BIND 9).
	Server A N', Server B N', Server C N', Server D N'.

	Now if you force everyone to wait until the child zone
	has progated.

	Server B updates NS RRset to N'.
	Server C transfers child zone from B.
	Server A updates NS RRset to N'.
	Server C transfers parent from A.
	Server D transfers parent zone from C.
	
	End state with modification (BIND 8/tinydns).
	Server A N', Server B N', Server C N', Server D N'.

	End state without modificatin (BIND 9).
	Server A N', Server B N', Server C N', Server D N'.

	You will notice that in all examples BIND 9 ends in the correct
	state.  The same cannot be said for BIND 8 or tinydns.

	Modification of SECONDARY zone content is NOT required or desirable
	for the correct operation of the DNS.

> > > Frequently the parent and child zone are under different administrative
> > > control, and are frequently on different servers. In such a case, the
> > > contents of the parent zone aren't merged with the child in the child's
> > > server, and no evidence of the inconsistency is seen through zone
> > > transfers. However, the inconsistency still exists and may still be
> > > visible by resolvers and nameservers that lookup the glue records.
> >
> > 	Nobody is claiming that inconsistancies don't occur all the
> > 	time.  What we are claiming is that those inconsistancies
> > 	need to be preserved in SECONDARY servers for the correct
> > 	operation of the DNS.  That they can only be corrected by
> > 	modifying the PRIMARY source of the zones.
> 
> ???  I can't parse this with respect to your previous statements. Could
> you rephrase it?

	You make changes at the PRIMARY server for the zone.
	You do not make changes to zones anywhere else.

> During the period in which the zone is inconsistent, there is no guarantee
> the zone will work.  Depending on the nature of the change, wrong
> information may be given in queries as well. Suppose the parent is
> removing control from the child, and has updated the glue to remove
> referals to the child nameservers. For some time (the TTL, at least), the
> original child servers will be queried.

	What does this have to do with this draft?
 
> On the other hand, the child zone may not even exist yet on the childs
> nameservers.  Referals to the zone fail.

	What does that have to do with this draft?
 
> To make a concrete example, Osama registers alquaeda.com, and begins
> coordinating his evil deeds. The registrar delegates the alquaeda.com as a
> child of .com. Eventually, the government intervenes, and .com replaces
> Osamas nameserver glue with new glue pointing to government servers. For a
> time, this zone will be inconsistent. Note that in this case, the zone
> transfers will not indicate the inconsistency.  However, for a short time,
> Osama will be able to put up a message warning his followers not to go to
> the government run site. This can't be avoided, no matter what gyrations
> you put AXFR through.

	What has this got to do with this draft?
 
> It makes no difference that the inconsistency _could_, _in_some_cases_, be
> seen at the secondaries.

	It does make a difference as demonstated above.
 
> > > You have obtained no benefits by these constraints.
> >
> > 	There are clear benefits in preserving zone contents on
> > 	SECONDARY servers.
> 
> Such as?
> 
> Your term "preserving zone contents" is misleading. The zone contents are
> not corrupted. The glue is inconsistent.  What is the benefit of
> preventing any trace of inconsistency in the secondary?

	It may be inconsistant but which version is correct?  The copy
	in the child may be out of date.
 
> It has nothing to do with IXFR. It has nothing to do with anything.

	IXFR still requires the content to only be changed in response
	to IXFR deltas.
 
> > > It is necessary, since the parent has glue records in the child zone.
> > > The parent therefore has (always) a part of the child zone. If that serve
> r
> > > also loads the child zone (or perhaps generates part of it dynamically),
> > > it quite reasonable to merge the records as though the zone includes
> > > multiple files, which in theory, it does.
> >
> > 	No it isn't.  Changes need to come from the PRIMARY source not
> > 	from intermediate sources.
> 
> The intermediate sources aren't making changes. They are, at worst,
> propogating old information mixed with new information. However, this is
> visible in other ways besides zone transfers.

	You are changing the contents if you mix data from different zones.
 
> > > The child zone contents will only be correct when the administrators of
> > > both zones agree on the contents of the glue records, and update their
> > > parts of the child zone accordingly. It will not be correct until then,
> > > regardless of how many zone transfers take place.
> >
> > 	Which is what I've been saying all along.  It doesn't require
> > 	a server to "correct" the content at a intermediate point.  Such
> > 	"corrections" actually cause problems.
> 
> Good. Then you agree that Bind 8 behavior is correct.

	BIND 8 "corrects" data at intermediate points.  BIND 9 doesn't.
	BIND 8's behaviour is wrong.
 
> > > > 	Nothing in RFC 1033 / 1034 / 1035 says that a server is permitt
> ed
> > > > 	to alter the content of a zone.  The responability for maintain
> ing
> > > > 	consistancy between zones is a administrative function.
> > >
> > > This is a loaded statement. The part of the server NOT involved in
> > > responding to queries and zone transfers is part of the administrative
> > > function. So, as part of that administrative function, it has to be able
> > > to modify the RR and zones accordingly.  Your proposed changes exclude a
> > > huge part of the potential for intelligence in name servers. And do so
> > > with no benefits.
> >
> > 	The benefits are correct operation of the DNS regardless of the
> > 	propogation timings involved.  If servers don't modify slave zone
> > 	content then which the master servers are brought into sync all
> > 	the servers will be brought into sync.
> 
> We already have correct operation of DNS. The zone contents are
> inconsistent until both adminstrators come to agreement. The child zone
> should be updated last. After the child zone is brought into agreement
> with the parent glue, zone transfers will be made which are correct. Only
> then will zone transfers will be correct.  Zone transfers made while the
> administrators are not in agreement will not be correct, even if there is
> no apparent evidence in the zone data from the child (such as a mixture of
> new and old glue) they are still incorrect. NS Queries against the parent
> and child servers will return different results.

	What have you been smoking?
 
> > 	This is not guarenteed if the zone content is modified by a
> > 	secondary server.
> >
> > > > > > > Strange, that was my reaction, too. I'm just trying to be polite.
>   77
> > > %
> > > > > > > work just fine. We don't want to break 77% of the servers out the
> re.
> > > > > >
> > > > > > 	You really think that it will break those servers?  LOL.
> > > > >
> > > > > They will not be compliant, and thus will need to be changed. Thus, t
> hey
> > > > > would be broken by definition of not being compliant.
> > > >
> > > > 	So.  Just because they will not be compliant doesn't mean
> > > > 	that that they need to be replaced immediately.  That
> > > > 	non-compliance doesn't hurt most of them.  For those where
> > > > 	it does have a negative impact it will mean that they should
> > > > 	be able to request a fix from their vendor.
> > >
> > > You seem to make a case that in general, non-compliance doesn't hurt
> > > anything. This is false, for both technical and commercial reasons.
> > > Technically, it hurts interoperability, which has some many obvious harms
> > > I won't go into them. Commercially, implementations make and advertise
> > > compatibility and standards compliance claims. This retroactively makes
> > > those claims false, which harms the business and reputation of those othe
> r
> > > vendors.
> >
> > 	They will be harmed much more if they don't correct a common
> > 	error now that it has been pointed out.
> 
> Except, there are no errors, beyond a window of inconsistency that cannot
> be avoided, and in fact, that window isn't fixed. Nor do you fix the
> "error". They are _still_ inconsistent for a period. And the child will
> _still_ have to be updated last.

	You obviously don't understand the problem
 
> > 	The claims were made in good faith and will be accepted as
> > 	such.
> 
> I'm not convinced.  If they were, we would have argued this before Bind 9
> was released, and before a book was sent out. Probably about 3 years ago.
> Someone knew years ago when they wrote the "backward compatibility" mode,
> that they had a protocol issue that would have to come before
> namedroppers.  That they delayed for so long doesn't indicate good faith
> to me.

	We having been saying for years before BIND 9 was released that
	that BIND 8 had this wrong.  BIND 9 conforms to RFC 1034.

	Axfr-clarify arose because it was pointed out that IXFR depended
	upon the definition of AXFR and that AXFR was not well specified.

> > > 77% will need a fix from the vendor, if we were to accept these changes.
> > >
> > > The vendor that made false claims of compatibility and standards
> > > compliance is Bind 9. It should suffer the commercial damage to its
> > > business and reputation, as a result.
> >
> > 	BIND 9 conforms to RFC 1034.  Nothing in RFC 1034 says to
> > 	merge zone content.  If fact 1034 says that this a administrative
> > 	responsability.
> 
> It does right now, due to a knowingly reckless exploitation of ambiguity
> in the AXFR. Once AXFR is clarified, Bind 9 will have to use its 'backward
> compatibility' mode to be compliant.

	What "reckless" exploitation? 
 
> It is "knowingly reckless" because the Bind 9 implementers _KNEW_ they
> needed to provide a "backward compatibility". That means they knew what
> they were doing was incompatible with any (all actually) reasonable
> interpretation (however ambiguous) of 1034.

	The only thing that requires a backward compatability switch
	is sending multiple records in a message.

	BIND 4 accepted these back in 1996.  Other vendors started
	accepting these back in 1996.  BIND 8 has always accepted
	them and could be configured to send them.  BIND 9 defaults
	to sending them and can be configured not to.

	At the same time as this was happening other vendors also
	started sending them.  We all knew that there was interoprability
	issues that were a result of oversites in the implementation.
	One vendor even made use of the fact that named (and I
	presume other servers) didn't barf on a oversized query to
	signal to it servers that they could send a multi-record
	respones.
 
> > > > > Your failure to comprehend the consequences of the changes does not l
> esse
> > > n
> > > > > the effect.  We now agree that these changes aren't necessary to supp
> ort
> > > > > IXFR. You were part of the bad engineering that led to the unnecessar
> y
> > > > > creation of these changes in Bind 9.  You were also part of the bad
> > > > > decision making that led to the distribution of these changes to Bind
>  9
> > > > > users prior to standardization, and quite possibly you were part of t
> he
> > > > > bad decision making that resulted in publishing a book on the subject
> ,
> > > > > prior to acceptance of your modifications to standards. In short, you
>  hav
> > > e
> > > > > shown bad judgement.
> > > >
> > > > 	I never said that they we not necessary for IXFR.  I said that
> > > > 	that your descripition of how to generate the differences was
> > > > 	irrelevent to this discussion.
> > >
> > > Ok, you are half way there. They are irrelevant because IXFR is
> > > irrelevant. These changes are not necessary to IXFR, as I explained that
> > > IXFR can work with the current AXFR, or even without AXFR.
> >
> > 	IXFR cannot work through SECONDARY servers that change zone
> > 	content regardless of whether the content was learnt via
> > 	AXFR or IXFR.
> 
> Sure it can.  It doesn't need AXFR at all.  And the secondary's aren't
> making arbitrary changes at all.

	If servers wern't making arbitary changes we would not be having
	this discussion.

> > > > 	It was bad engineering to merge the data sets together in the
> > > > 	first place.  It was not required by RFC 1033/ 1034 / 1035.
> > > > 	It had negative consequences.  It was good engineering to
> > > > 	correct this.  It was also good engineering to report a
> > > > 	common error to the community so that other vendors could
> > > > 	fix their mistakes.
> > >
> > > Actually, since the parent has the glue in the child zone, it has part of
> > > the child zone as well as the master zone.  Merging them together is not
> > > prohibited, and in the case where child and parent have the same
> > > adminstrator, as might be the case where most of the child is simply
> > > automatically generated by the nameserver, can make things much easier.
> > >
> > > Your constraints preclude this unnecessarilly.
> >
> > 	The constraint in on the SECONDARY server.
> 
> So? It is still unnecesary.

	Next you will tell me that the grass is blue and the sky is green.

	If you can't see the need for the constraint stop blocking those
	that do.

> > > Since I can think of cases where it is useful to merge records together,
> > > it is bad engineering to remove that flexibility and obtain no benefits i
> n
> > > return.
> > >
> > > > > Trying to "belittle" the effects with the "LOL", as opposed to offeri
> ng
> > > > > anything substantive, simply suggests that you have no appreciation o
> f th
> > > e
> > > > > seriousness of the changes.  Perhaps you should take this more seriou
> sly.
> > > >
> > > > 	I'm quite aware of what the change requires.  I'm also aware
> > > > 	that most of the nameserver are used in situations where
> > > > 	the zone contents is already preserved because they are not
> > > > 	serving zones with parent / child relationships.
> > >
> > > Apparently, you aren't even aware that your changes will make all non-bin
> d
> > > 9 servers non-compliant.  Had you been aware of that, it seems you would
> > > have brought this proposal forward something like 3 years ago, before
> > > releasing Bind 9, and before publishing a book on the subject.
> >
> > 	Well you obviously have not been reading.  ISC is not the
> > 	only vendor to come to the same conclusion about preserving
> > 	zone content.  I suspect that they are just bored with
> > 	arguing with you and Dan.
> 
> I think they just haven't really read the proposal's, and have taken some
> misleading assurances at face value.
> 
> > > > 	Anyone saying that all the nameservers need to be replaced
> > > > 	immediately is spreading FUD.  LOL the the correct reponse
> > > > 	to FUD.
> > >
> > > Making 77% of the servers non-compliant is a fact of your proposed
> > > changes.  It is another fact, as explained, that non-compliant servers
> > > will need to be replaced.  Will they suddenly stop working? It depends on
> > > whether other implementations want to implement a "backwards
> > > compatibility" mode. If they don't implement this mode, then the answer i
> s
> > > yes, they will stop working as soon as these updates are deployed by othe
> r
> > > vendors. Of course, this is a bad result.
> >
> > 	Well they havn't stopped working in the last two years that
> > 	this code has been out there.  Nothing in this drafts stops
> > 	a server implementing it taking to any other server.
> 
> Uhh, wrong. The drafts make the current AXFR non-compliant. There is
> nothing that would require a server to implement the old AXFR and provide
> a "backwards compatibility" mode such as Bind 9 has.

	So you want

   "Slaves MUST accept messages containing any number of answer RRs.  For
   compatibility with old slaves, masters that support sending multiple
   answers per message SHOULD be configurable to revert to the
   historical mode of one answer per message, and the configuration
   SHOULD be settable on a per-slave basis."

	replaced with

   "Slaves MUST accept messages containing any number of answer RRs.  For
   compatibility with old slaves, masters that support sending multiple
   answers per message MUST be configurable to revert to the
   historical mode of one answer per message, and the configuration
   SHOULD be settable on a per-slave basis."

> So servers running today, won't be able to talk to strictly compliant
> servers that don't have a backwards compatibility mode.

> > 	There is one backwards compatiblity switch which is only
> > 	requires if you decide to send multiple records in a single
> > 	messages.  A server is not required to send multiple records
> > 	in a single message.
> 
> But is allowed to, and a server that can't receive such messages won't be
> able to get the zone.
> 
> > > > > 1) It doesn't say that it adds a completely new, incompatible zone
> > > > > transfer protocol.  New protocols should be made through a different
> > > > > process, which includes experimentation. I'm not against experimentin
> g
> > > > > with a new protocol. Indeed, I think this idea has some merit. Howeve
> r, i
> > > t
> > > > > can't be "end-run standardized" by a "clarification". There is a proc
> ess.
> > > >
> > > > 	It isn't new.  All it is saying is that the contents tramitted
> > > > 	out MUST be that transmitted in.  This occurs most of the time
> > > > 	already.  Note BIND is not the only implementation that does
> > > > 	this.  We have already had reports of 3 other implementations
> > > > 	doing this.  Even the implementations that don't guarentee the
> > > > 	contents do this most of the time.  It has no negative effects.
> > >
> > > No, Section 3.1 is a whole new derivative of AXFR. That is new.
> >
> > 	Actually it's always been allowed by RFC 1034.  Just because
> > 	it wasn't implement initially doesn't mean that it was not
> > 	allowed.
> 
> Uhh, wrong, except in an unreasonably broad technical exception due to the
> vagueness of 1034.

	Multiple records in the answer section have always been part
	of the standard.
 
> > > > > 4) It doesn't say that it changes the definition of zone data to be
> > > > > public. Zone data is absolutely not "public by definition". It could 
> very
> > > > > well be useful to tag certain RRs as non-public, and exclude them fro
> m
> > > > > zone transfers to public servers. This "clarification" precludes that
> .
> > > > > This is really 2 changes.
> > > >
> > > > 	Nowhere in RFC 1033 / 1034 / 1035 does it say that zone transfe
> rs
> > > > 	are restricted to secondaries.  Nowhere in RFC 1033 / 1034 / 10
> 35
> > > > 	does it say that you should restrict zone tranfers.
> > >
> > > I don't think you understood my statement. I'm talking about the
> > > definition of zone data. Nowhere does 1034 etc say that zone data is
> > > public.  It may well have been thought to be public, originally, but sinc
> e
> > > I can easily see a useful purpose in withholding some private RRs, there
> > > isn't any reason to preclude that behavior.
> >
> > 	Does this address your concerns?
> 
> No. Because it might be reasonable not to give complete zone data.
> 
> >    "The zone transfer protocol allows read-only access to the complete
> >    zone data.  When the data being served to the public it is
> >    generally acceptable to allow unrestricted access to it via AXFR.
> >    Sites that wish to avoid disclosing their full zone data MAY
> >    restrict zone transfer access to authorized slaves."
> >
> > 	If you have part of a zone to which you would normally
> > 	return REFUSED to I suggest that you also return REFUSED
> > 	to AXFR.
> >
> > 	If you want to be able to return partial zones then I suggest
> > 	that a new TYPE be defined so that receipients can know
> > 	that the results will be incomplete.
> 
> So far as the secondary is concerned, the zone is complete.  If you do
> this, you don't want to tell people that you have some data that isn't
> public.  Nor would you ever need to.

	Well if you don't want to tell them that you have private
	part then you won't be answering with REFUSED. You effectively
	have two zones that just have a lot in common.  Treat them
	as such.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Fri Feb 21 02:33:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22028;
	Fri, 21 Feb 2003 02:33:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m7lO-0007Ol-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 02:38:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m7iV-00070S-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 02:35:31 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21825
	for <ietf@ietf.org>; Fri, 21 Feb 2003 02:26:39 -0500 (EST)
Received: (qmail 48795 invoked by uid 1016); 21 Feb 2003 07:30:55 -0000
Date: 21 Feb 2003 07:30:55 -0000
Message-ID: <20030221073055.48794.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: axfr-clarify's fraudulent claims of consensus
References: <20030214103228.71052.qmail@cr.yp.to> <200302101659.LAA15654@ietf.org> <10697.1045222702@munnari.OZ.AU> <20030215033141.82623.qmail@cr.yp.to> <20030220150752.357be0cc.moore@cs.utk.edu> <20030220210623.40638.qmail@cr.yp.to> <3E5551DB.2060808@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Eliot Lear writes:
> your implementation

And others, notably BIND 8. We're talking about MOST of the Internet's
DNS servers here. (See http://cr.yp.to/surveys/dns1.html; I'm assuming
that *.com is representative.) This is not a small issue.

> could cause interoperability problems by potentially allowing for
> different contents of the same zone with the same serial number.

No. The _administrator_ can create problems by violating RFC 1034.
(Andrews has admitted that his broken configurations violate RFC 1034.)

If the administrator follows RFC 1034's consistency requirements, no
problems occur. In fact, if the administrator violates RFC 1034 but
still follows the easy semi-synchronization rule, no problems occur.

Andrews is finally coming out of the closet and arguing that the RFC
1034 rule should be changed (because, with his software, the rule is
hard for administrators to follow). But he can't reasonably argue
against the semi-synchronization rule. People normally follow that rule
anyway; there's no reason to break it; and it guarantees that problems
don't occur.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 21 03:35:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22943;
	Fri, 21 Feb 2003 03:35:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m8hR-0001Fm-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 03:38:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m8dd-00018I-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 03:34:33 -0500
Received: from nwkea-mail-1.sun.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22775;
	Fri, 21 Feb 2003 03:25:40 -0500 (EST)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA00422;
	Fri, 21 Feb 2003 00:29:28 -0800 (PST)
Received: from lillen (punchin-nordmark.Eng.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id h1L8TMP07931;
	Fri, 21 Feb 2003 09:29:23 +0100 (MET)
Date: Fri, 21 Feb 2003 09:25:36 +0100 (CET)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
To: Dean Anderson <dean@av8.com>
Cc: Mark.Andrews@isc.org, mw-list-namedroppers@csi.hu,
        Name Droppers <namedroppers@ops.ietf.org>, ietf@ietf.org,
        iesg@ietf.org
In-Reply-To: "Your message with ID" <Pine.LNX.4.44.0302201959400.13516-100000@commander.av8.net>
Message-ID: <Roam.SIMC.2.0.6.1045815936.14452.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

> Apparently, you aren't even aware that your changes will make all non-bind
> 9 servers non-compliant.  Had you been aware of that, it seems you would
> have brought this proposal forward something like 3 years ago, before
> releasing Bind 9, and before publishing a book on the subject.

A data point.

http://www.ietf.org/proceedings/00jul/I-D/dnsext-axfr-clarify-00.txt
INTERNET-DRAFT                                      Andreas Gustafsson
draft-ietf-dnsext-axfr-clarify-00.txt                     Nominum Inc.
                                                            March 2000
Seems to be 3 years ago.

  Erik




From owner-ietf@ietf.org  Fri Feb 21 03:45:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23224;
	Fri, 21 Feb 2003 03:45:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m8s6-0002LG-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 03:49:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m8qZ-0002H5-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 03:47:55 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23095;
	Fri, 21 Feb 2003 03:38:59 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1L8gX4U011674;
	Fri, 21 Feb 2003 19:42:34 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302210842.h1L8gX4U011674@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-reply-to: Your message of "21 Feb 2003 07:30:55 -0000."
             <20030221073055.48794.qmail@cr.yp.to> 
Date: Fri, 21 Feb 2003 19:42:33 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Eliot Lear writes:
> > your implementation
> 
> And others, notably BIND 8. We're talking about MOST of the Internet's
> DNS servers here. (See http://cr.yp.to/surveys/dns1.html; I'm assuming
> that *.com is representative.) This is not a small issue.
> 
> > could cause interoperability problems by potentially allowing for
> > different contents of the same zone with the same serial number.
> 
> No. The _administrator_ can create problems by violating RFC 1034.
> (Andrews has admitted that his broken configurations violate RFC 1034.)

	The administrator cannot avoid breaking the rule.  All they
	can do is ensure that the time the rule is broken is
	minimised.
 
> If the administrator follows RFC 1034's consistency requirements, no
> problems occur. In fact, if the administrator violates RFC 1034 but
> still follows the easy semi-synchronization rule, no problems occur.

	You don't live in the real world if you think there won't be
	errors.  The job of computers is to make life easier not
	more complicated.  Having a protocol/implementation that
	doesn't deal with timing mistakes is a bad.
	
> Andrews is finally coming out of the closet and arguing that the RFC
> 1034 rule should be changed (because, with his software, the rule is
> hard for administrators to follow). But he can't reasonably argue
> against the semi-synchronization rule. People normally follow that rule
> anyway; there's no reason to break it; and it guarantees that problems
> don't occur.

	Dan if you want everyone to follow this rule then are you
	going to modify your software to enforce it.  You software
	doesn't currently comply with this rule.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Fri Feb 21 04:26:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22944;
	Fri, 21 Feb 2003 03:35:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18m8ch-00016Y-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 03:33:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m8cZ-00014F-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 03:33:27 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA22755;
	Fri, 21 Feb 2003 03:24:33 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1L8S64U011586;
	Fri, 21 Feb 2003 19:28:06 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302210828.h1L8S64U011586@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-reply-to: Your message of "21 Feb 2003 06:37:25 -0000."
             <20030221063725.35914.qmail@cr.yp.to> 
Date: Fri, 21 Feb 2003 19:28:06 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Mark.Andrews@isc.org writes:
> > Whenever you have a parent and child zones under different administrative
> > controls it is impossible to change both zones simultaniously.
> 
> False.
> 
> Set the clocks correctly, and schedule the change on all the servers for
> a particular time, using (for example) the tinydns timestamp feature
> described in http://cr.yp.to/djbdns/tinydns-data.html. When that time
> rolls around, all the servers will change their data simultaneously, as
> RFC 1034 requires.

	So now you want to extend the protocol so that each record has
	an inception time and a expiration time.  We could create a
	new transfer protocol to do this and treat this data as meta
	data.

	However you would still have the problem of the meta data
	being inconsitant.  You would still need to ensure that it
	is transmitted in the right order or that servers didn't
	modify it while it was being transmitted or that you ban
	any server but the master server sending copies of the zone.

	The problems are inherent with having different source maintaining
	copies of the same data.
	
	Mark

> Yes, this is difficult to achieve with BIND, AXFR, etc. But it's easy to
> achieve with better software, better replication protocols, etc. You're
> making a fool of yourself when you call it ``impossible.''
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Fri Feb 21 10:18:04 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03083;
	Fri, 21 Feb 2003 10:18:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mEk0-0005ul-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 10:05:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mEiJ-0005qA-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 10:03:47 -0500
Received: from shell.nominum.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01879;
	Fri, 21 Feb 2003 09:54:49 -0500 (EST)
Received: from nominum.com (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with ESMTP
	id AE375137F06; Fri, 21 Feb 2003 06:58:38 -0800 (PST)
Date: Fri, 21 Feb 2003 06:58:42 -0800
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: Dean Anderson <dean@av8.com>, Mark_Andrews@isc.org,
        mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        ietf@ietf.org, iesg@ietf.org
To: Erik Nordmark <Erik.Nordmark@sun.com>
From: David Conrad <david.conrad@nominum.com>
In-Reply-To: <Roam.SIMC.2.0.6.1045815936.14452.nordmark@bebop.france>
Message-Id: <F7CF1F52-45AC-11D7-A854-000393DB42B2@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I remember when people thought OSI protocols took too long to 
standardize... :-)

Rgds,
-drc

On Friday, February 21, 2003, at 12:25  AM, Erik Nordmark wrote:

>> Apparently, you aren't even aware that your changes will make all 
>> non-bind
>> 9 servers non-compliant.  Had you been aware of that, it seems you 
>> would
>> have brought this proposal forward something like 3 years ago, before
>> releasing Bind 9, and before publishing a book on the subject.
>
> A data point.
>
> http://www.ietf.org/proceedings/00jul/I-D/dnsext-axfr-clarify-00.txt
> INTERNET-DRAFT                                      Andreas Gustafsson
> draft-ietf-dnsext-axfr-clarify-00.txt                     Nominum Inc.
>                                                             March 2000
> Seems to be 3 years ago.
>
>   Erik
>
>
> _______________________________________________
> This message was passed through ietf_censored@carmen.ipv6.cselt.it, 
> which is a sublist of ietf@ietf.org. Not all messages are passed. 
> Decisions on what to pass are made solely by Raffaele D'Albenzio.
>




From owner-ietf@ietf.org  Fri Feb 21 12:36:52 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08150;
	Fri, 21 Feb 2003 12:36:52 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mH77-0000k0-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 12:37:33 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mH6W-0000gW-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 12:36:56 -0500
Received: from fnal.gov (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07863;
	Fri, 21 Feb 2003 12:27:57 -0500 (EST)
Received: from gungnir.fnal.gov ([131.225.80.1])
 by smtp.fnal.gov (PMDF V6.0-24 #37519)
 with ESMTP id <0HAO00L7P6102V@smtp.fnal.gov>; Fri,
 21 Feb 2003 11:31:49 -0600 (CST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.11.6+Sun/8.11.6) with ESMTP id h1LHVmG29919; Fri,
 21 Feb 2003 11:31:48 -0600 (CST)
Date: Fri, 21 Feb 2003 11:31:48 -0600
From: Matt Crawford <crawdad@fnal.gov>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification
In-reply-to: "21 Feb 2003 06:37:25 GMT." <20030221063725.35914.qmail@cr.yp.to>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Message-id: <200302211731.h1LHVmG29919@gungnir.fnal.gov>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Set the clocks correctly, and schedule the change on all the servers for
> a particular time, using (for example) the tinydns timestamp feature
> described in http://cr.yp.to/djbdns/tinydns-data.html. When that time
> rolls around, all the servers will change their data simultaneously, 

My friend Dr. Einstein would like a word with you about your casual
misuse of the word "simultaneously."

__________________________________________________________________
Matt Crawford             crawdad@fnal.gov                Fermilab



From owner-ietf@ietf.org  Fri Feb 21 13:11:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09556;
	Fri, 21 Feb 2003 13:11:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mHgv-0007FW-00
	for ietf-list@ran.ietf.org; Fri, 21 Feb 2003 13:14:33 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mHgf-0007BO-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 13:14:17 -0500
Received: from fnal.gov (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09395;
	Fri, 21 Feb 2003 13:05:17 -0500 (EST)
Received: from gungnir.fnal.gov ([131.225.80.1])
 by smtp.fnal.gov (PMDF V6.0-24 #37519)
 with ESMTP id <0HAO005A67R9QY@smtp.fnal.gov>; Fri,
 21 Feb 2003 12:09:09 -0600 (CST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.11.6+Sun/8.11.6) with ESMTP id h1LI98G03298; Fri,
 21 Feb 2003 12:09:08 -0600 (CST)
Date: Fri, 21 Feb 2003 12:09:08 -0600
From: Matt Crawford <crawdad@fnal.gov>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification
In-reply-to: "21 Feb 2003 06:58:42 PST."
 <F7CF1F52-45AC-11D7-A854-000393DB42B2@nominum.com>
To: David Conrad <david.conrad@nominum.com>
Cc: Erik Nordmark <Erik.Nordmark@sun.com>,
        Name Droppers <namedroppers@ops.ietf.org>, ietf@ietf.org,
        iesg@ietf.org
Message-id: <200302211809.h1LI98G03298@gungnir.fnal.gov>
Sender: owner-ietf@ietf.org
Precedence: bulk

> > draft-ietf-dnsext-axfr-clarify-00.txt                 Nominum Inc.
> >                                                         March 2000
> > Seems to be 3 years ago.
> I remember when people thought OSI protocols took too long to 
> standardize... :-)

"$X is a slow-moving parody of itself." -- Peter Honeyman

In the original, $X was bound to "USENET", not "IETF".




From owner-ietf@ietf.org  Sat Feb 22 01:11:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25802;
	Sat, 22 Feb 2003 01:11:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mSk3-0003mm-00
	for ietf-list@ran.ietf.org; Sat, 22 Feb 2003 01:02:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mSjd-0003k7-00
	for ietf@ran.ietf.org; Sat, 22 Feb 2003 01:02:05 -0500
Received: from dhcp-168-17-124.autonomica.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25644
	for <ietf@ietf.org>; Sat, 22 Feb 2003 00:52:52 -0500 (EST)
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by dhcp-168-17-124.autonomica.se (8.12.6/8.10.2) with ESMTP id h1M5vLif008685;
	Sat, 22 Feb 2003 06:57:32 +0100 (CET)
Date: Fri, 21 Feb 2003 16:32:40 +0100
Subject: Re: Warning about the use of abusive language
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: ietf@ietf.org
To: grenville armitage <garmitage@swin.edu.au>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <3E54DFCF.61CEA099@swin.edu.au>
Message-Id: <B662E4EC-45B1-11D7-932B-000393AB1404@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
> "Be liberal in what you accept" seems a good philosophy for reading 
> this
> list...
>

As a very intelligent man told me once - "The good thing about 
'Subject' is that you know what you can delete without reading it".

- kurtis -




From owner-ietf@ietf.org  Sat Feb 22 13:23:19 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14080;
	Sat, 22 Feb 2003 13:23:19 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18meBN-0005Kc-00
	for ietf-list@ran.ietf.org; Sat, 22 Feb 2003 13:15:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18meAW-0005JL-00
	for ietf@ran.ietf.org; Sat, 22 Feb 2003 13:14:36 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13939
	for <ietf@ietf.org>; Sat, 22 Feb 2003 13:05:22 -0500 (EST)
Received: from as.vix.com (localhost [127.0.0.1])
	by as.vix.com (Postfix) with ESMTP id 02C03379EF3
	for <ietf@ietf.org>; Sat, 22 Feb 2003 18:09:14 +0000 (GMT)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: has everybody who submitted a draft since decmber gotten this message?
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Mailer: MH-E 7.2; nmh 1.0.4; GNU Emacs 21.2.1
Date: Sat, 22 Feb 2003 18:09:14 +0000
Message-Id: <20030222180914.02C03379EF3@as.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

--=-=-=

or am i hitting something unusual?


--=-=-=
Content-Type: message/rfc822
Content-Disposition: attachment; filename=30
Content-Description: forwarded message

Return-Path: <scoya@ietf.org>
X-Original-To: paul@vix.com
Delivered-To: vixie@as.vix.com
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by as.vix.com (Postfix) with ESMTP id 2D45C379EF8
	for <paul@vix.com>; Sat, 22 Feb 2003 17:44:44 +0000 (GMT)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA13670;
	Sat, 22 Feb 2003 12:40:50 -0500 (EST)
Date: Sat, 22 Feb 2003 12:40:50 -0500 (EST)
Message-Id: <200302221740.MAA13670@ietf.org>
To: paul@vix.com
Subject: Re: please assign me a file name for the -00 edition of a dnsop draft
References: <20030222174440.1F7B6379E40@as.vix.com>
In-Reply-To: <20030222174440.1F7B6379E40@as.vix.com>
X-URL: http://www.ietf.org/
Reply-To: nsyracus@ietf.org
Subject: Autoreply from Internet Draft Submission Manager
From: ietfauto@ietf.org (Internet Draft Submission Manager)
MIME-Version: 1.0

Hello,

This message is being sent to acknowledge receipt of your submission
or message to internet-drafts@ietf.org

The I-D administrator will be out of the office from December 23rd until Monday,
January 6, 2003. All submissions will be processed.

Thank you. We appreciate your understanding and patience.

Have a wonderful and joyous holiday season.

Internet-Drafts Administrator

--=-=-=--



From owner-ietf@ietf.org  Sat Feb 22 18:47:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17513;
	Sat, 22 Feb 2003 18:47:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mj88-0001gd-00
	for ietf-list@ran.ietf.org; Sat, 22 Feb 2003 18:32:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mj7C-0001g9-00
	for ietf@ran.ietf.org; Sat, 22 Feb 2003 18:31:30 -0500
Received: from mail1.microsoft.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17270
	for <ietf@ietf.org>; Sat, 22 Feb 2003 18:22:13 -0500 (EST)
Received: from inet-vrs-01.redmond.corp.microsoft.com ([157.54.8.27]) by mail1.microsoft.com with Microsoft SMTPSVC(5.0.2195.6659);
	 Sat, 22 Feb 2003 15:26:04 -0800
Received: from 157.54.5.25 by inet-vrs-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 22 Feb 2003 15:26:04 -0800
Received: from RED-IMC-01.redmond.corp.microsoft.com ([157.54.9.102]) by INET-HUB-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3765.0);
	 Sat, 22 Feb 2003 15:26:04 -0800
Received: from WIN-IMC-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by RED-IMC-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Sat, 22 Feb 2003 15:26:03 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by WIN-IMC-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3765.0);
	 Sat, 22 Feb 2003 15:26:00 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6851.8
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: FW: Autoreply from Internet Draft Submission Manager
Date: Sat, 22 Feb 2003 15:26:00 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA1D2B9B@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Autoreply from Internet Draft Submission Manager
thread-index: AcLauLEFmZyFrdx+QNODSaM64OqFxAAEORVI
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 22 Feb 2003 23:26:01.0101 (UTC) FILETIME=[C2C8B3D0:01C2DAC9]
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA17513

This automatic reply from the Internet Draft submission would have us believe that the holiday season is still going on...

________________________________

From: Internet Draft Submission Manager [mailto:ietfauto@ietf.org]
Sent: Sat 2/22/2003 1:19 PM
To: Christian Huitema
Subject: Autoreply from Internet Draft Submission Manager



Hello,

This message is being sent to acknowledge receipt of your submission
or message to internet-drafts@ietf.org

The I-D administrator will be out of the office from December 23rd until Monday,
January 6, 2003. All submissions will be processed.

Thank you. We appreciate your understanding and patience.

Have a wonderful and joyous holiday season.

Internet-Drafts Administrator





From owner-ietf@ietf.org  Sun Feb 23 01:57:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22689;
	Sun, 23 Feb 2003 01:57:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mpyy-0002Xf-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 01:51:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mpym-0002X5-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 01:51:16 -0500
Received: from nixon.xkey.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22584
	for <ietf@ietf.org>; Sun, 23 Feb 2003 01:41:53 -0500 (EST)
Received: (qmail 21338 invoked by uid 1087); 23 Feb 2003 06:45:43 -0000
MBOX-Line: From ietf_censored-admin@vesuvio.ipv6.tilab.com  Fri Feb 21 22:24:26 2003
Delivered-To: dan@xkey.com
Received: (qmail 6478 invoked from network); 22 Feb 2003 06:24:26 -0000
Received: from ns11.dnsprotect.com (HELO velocity.dnsprotect.com) (209.50.252.235)
  by h42-rt.sv.meer.net with SMTP; 22 Feb 2003 06:24:26 -0000
Received: from [163.162.170.199] (helo=vesuvio.ipv6.cselt.it)
	by velocity.dnsprotect.com with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 3.36 #1)
	id 18mT4S-0004bp-00
	for dan@dankohn.com; Sat, 22 Feb 2003 01:23:37 -0500
Received: from vesuvio.ipv6.cselt.it (localhost.ipv6.cselt.it [127.0.0.1])
	by vesuvio.ipv6.cselt.it (8.12.6/8.12.6) with ESMTP id h1M6CIJE084002;
	Sat, 22 Feb 2003 07:12:19 +0100 (CET)
	(envelope-from ietf_censored-admin@vesuvio.ipv6.tilab.com)
Received: from carmen.ipv6.tilab.com (carmen.ipv6.tilab.com [163.162.170.198])
	by vesuvio.ipv6.cselt.it (8.12.6/8.12.6) with ESMTP id h1M6AxJE083987
	for <ietf_censored@ngnet.it>; Sat, 22 Feb 2003 07:10:59 +0100 (CET)
	(envelope-from owner-ietf_censored@ngnet.it)
Received: from ran.ietf.org (ran.ietf.org [132.151.6.60])
	by carmen.ipv6.tilab.com (8.12.3/8.12.3) with ESMTP id h1M6DK6G028368
	for <ietf_censored@carmen.ipv6.cselt.it>; Sat, 22 Feb 2003 07:13:21 +0100 (MET)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18mSk3-0003mm-00
	for ietf-list@ran.ietf.org; Sat, 22 Feb 2003 01:02:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mSjd-0003k7-00
	for ietf@ran.ietf.org; Sat, 22 Feb 2003 01:02:05 -0500
Received: from dhcp-168-17-124.autonomica.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25644
	for <ietf@ietf.org>; Sat, 22 Feb 2003 00:52:52 -0500 (EST)
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by dhcp-168-17-124.autonomica.se (8.12.6/8.10.2) with ESMTP id h1M5vLif008685;
	Sat, 22 Feb 2003 06:57:32 +0100 (CET)
Subject: Re: Warning about the use of abusive language
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: ietf@ietf.org
Old-To: grenville armitage <garmitage@swin.edu.au>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <3E54DFCF.61CEA099@swin.edu.au>
Message-Id: <B662E4EC-45B1-11D7-932B-000393AB1404@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf_censored@vesuvio.ipv6.tilab.com
X-Mailman-Version: 2.0.13
List-Unsubscribe: <http://vesuvio.ipv6.tilab.com/mailman/listinfo/ietf_censored>,
	<mailto:ietf_censored-request@vesuvio.ipv6.tilab.com?subject=unsubscribe>
List-Id: <ietf_censored.vesuvio.ipv6.tilab.com>
List-Post: <mailto:ietf_censored@vesuvio.ipv6.tilab.com>
List-Help: <mailto:ietf_censored-request@vesuvio.ipv6.tilab.com?subject=help>
List-Subscribe: <http://vesuvio.ipv6.tilab.com/mailman/listinfo/ietf_censored>,
	<mailto:ietf_censored-request@vesuvio.ipv6.tilab.com?subject=subscribe>
List-Archive: <http://vesuvio.ipv6.tilab.com/pipermail/ietf_censored/>
Date: Fri, 21 Feb 2003 16:32:40 +0100
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - velocity.dnsprotect.com
X-AntiAbuse: Original Domain - dankohn.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - vesuvio.ipv6.tilab.com
Status: O
To: dmk@skymv.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
> "Be liberal in what you accept" seems a good philosophy for reading 
> this
> list...
>

As a very intelligent man told me once - "The good thing about 
'Subject' is that you know what you can delete without reading it".

- kurtis -


_______________________________________________
This message was passed through ietf_censored@carmen.ipv6.cselt.it, which is a sublist of ietf@ietf.org. Not all messages are passed. Decisions on what to pass are made solely by Raffaele D'Albenzio.




From owner-ietf@ietf.org  Sun Feb 23 04:19:46 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04620;
	Sun, 23 Feb 2003 04:19:46 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18msJB-0004yX-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 04:20:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18msJ1-0004xu-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 04:20:19 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04560
	for <ietf@ietf.org>; Sun, 23 Feb 2003 04:10:55 -0500 (EST)
Received: (qmail 85300 invoked by uid 1016); 23 Feb 2003 09:15:13 -0000
Date: 23 Feb 2003 09:15:13 -0000
Message-ID: <20030223091513.85299.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: update timing errors
References: <20030223022932.83480.qmail@cr.yp.to> <200302230507.h1N57m4U019531@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> If you never update the child then it is an *administrative* error.

Changing the serial number too early is also an administrative error.
Here's a summary of our three examples of administrative errors:

   1. Failing to update the parent serial number after updating the glue
      in all the child servers. As you keep pointing out, this error can
      cause problems with BIND 8: the data will be inconsistent until
      the serial number is updated.

   2. Failing to update the parent serial number after updating the glue
      in the parent master. This error can cause problems with BIND 9
      (and BIND 8, of course): the data will be inconsistent until the
      serial number is updated.

   3. Failing to update the data in the child master. This error can
      cause problems with BIND 9 (and BIND 8, of course): the data will
      be inconsistent until the child data is updated (and the serial
      numbers handled properly).

In every case, the administrator is violating RFC 1034 (as you have
admitted), and is creating a configuration that does not work properly
with most DNS software deployed in the real world.

You persist in drawing a completely unjustified line between the first
error and the other two errors. You claim that allowable administrative
action is defined by BIND 9---never mind what RFC 1034 says, and never
mind the rest of the installed base. You cycle endlessly between ``BIND
9 is doing the Right Thing'' and ``BIND 9 handles that situation'' and
``that situation is not actually an error,'' attempting to defend each
part of the BIND 9 religion by showing how it fits with the other parts.
The circularity is pathetic.

In situations where there's a difference between the software and the
spec---for example, actions that are prohibited by RFC 1034 even though
they work in the real world, or vice versa---one can reasonably discuss
whether the actions should be considered errors. But the above actions
do _not_ work and are _not_ allowed by the spec. If you want to support
them in BIND 9, fine, but you have no basis for demanding that the rest
of us support them too.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Sun Feb 23 16:43:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13169;
	Sun, 23 Feb 2003 16:43:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18n3lU-0008GD-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 16:34:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18n3lC-0008Fk-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 16:34:10 -0500
Received: from drugs.dv.isc.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA12994;
	Sun, 23 Feb 2003 16:24:36 -0500 (EST)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.12.6/8.12.6) with ESMTP id h1NLS74U020848;
	Mon, 24 Feb 2003 08:28:09 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200302232128.h1NLS74U020848@drugs.dv.isc.org>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
From: Mark.Andrews@isc.org
Subject: Re: update timing errors 
In-reply-to: Your message of "23 Feb 2003 09:15:13 -0000."
             <20030223091513.85299.qmail@cr.yp.to> 
Date: Mon, 24 Feb 2003 08:28:07 +1100
Sender: owner-ietf@ietf.org
Precedence: bulk


> Mark.Andrews@isc.org writes:
> > If you never update the child then it is an *administrative* error.
> 
> Changing the serial number too early is also an administrative error.
> Here's a summary of our three examples of administrative errors:
> 
>    1. Failing to update the parent serial number after updating the glue
>       in all the child servers. As you keep pointing out, this error can
>       cause problems with BIND 8: the data will be inconsistent until
>       the serial number is updated.
> 
>    2. Failing to update the parent serial number after updating the glue
>       in the parent master. This error can cause problems with BIND 9
>       (and BIND 8, of course): the data will be inconsistent until the
>       serial number is updated.
> 
>    3. Failing to update the data in the child master. This error can
>       cause problems with BIND 9 (and BIND 8, of course): the data will
>       be inconsistent until the child data is updated (and the serial
>       numbers handled properly).
> 
> In every case, the administrator is violating RFC 1034 (as you have
> admitted), and is creating a configuration that does not work properly
> with most DNS software deployed in the real world.
> 
> You persist in drawing a completely unjustified line between the first
> error and the other two errors. You claim that allowable administrative
> action is defined by BIND 9---never mind what RFC 1034 says, and never
> mind the rest of the installed base. You cycle endlessly between ``BIND
> 9 is doing the Right Thing'' and ``BIND 9 handles that situation'' and
> ``that situation is not actually an error,'' attempting to defend each
> part of the BIND 9 religion by showing how it fits with the other parts.
> The circularity is pathetic.
> 
> In situations where there's a difference between the software and the
> spec---for example, actions that are prohibited by RFC 1034 even though
> they work in the real world, or vice versa---one can reasonably discuss
> whether the actions should be considered errors. But the above actions
> do _not_ work and are _not_ allowed by the spec. If you want to support
> them in BIND 9, fine, but you have no basis for demanding that the rest
> of us support them too.

	Changing the content of SECONDARY zones is outside of the
	actions specified by RFC 1034.  In fact RFC 1034 demands a
	"accurate" copy.  You can't have a "accurate" copy if it
	has been changed.

	There are no timing issues if you have a "accurate" copy.

	There is no such thing as changing the serial "too early".

	It is the errors in BIND 4, BIND 8 and tinydns that introduce
	timing constraints that are not part of RFC 1034 and only
	affect servers that are serving both parent and child zones.

	We have heard from at least three other independent developers
	that they preserve / preserved the copy of the child zone
	based on RFC 1034 requirement.

	Maintaining consistancy between parent and child zones is
	a administrative responsability.  Even with automated
	assistance the changes are required to be applied to the
	PRIMARY not to the SECONDARY.  BIND 4, BIND 8 and tinydns
	violate the maintance model as a result of applying changes
	in the incorrect place directly leading to the situation where
	all the PRIMARY copies of the zones have the correct information
	but some of the SECONDARY "copies" don't.

	There is no technical reason not to preserve the contents of
	the SECONDARY copies of the zone unaltered.  There are no
	negative effects from doing this.  There definitely are negative
	effects caused by changing the contents of SECONDARY copies.

	All your complaints are based on your interpretation of RFC
	1034.  Your interpretation introduces timing issues which
	even your own software cannot meet without violating the
	requirement to change the serial number when you change the
	zone contents.

	In addition to the pure AXFR issues.  IXFR depends upon the
	contents of the zone not being changed unilaterally on the
	SECONDARY.  Failure to preserve the contents will result
	in deltas not applying that should.  This should result in
	fallback to AXFR to get a upto date copy of the zone.  This
	will result in a AXFR style IXFR to done stream servers.

	Mark

--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org



From owner-ietf@ietf.org  Sun Feb 23 18:06:58 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14618;
	Sun, 23 Feb 2003 18:06:58 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18n5ES-0000vk-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 18:08:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18n5DZ-0000vC-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 18:07:33 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14517;
	Sun, 23 Feb 2003 17:58:01 -0500 (EST)
Received: from as.vix.com (localhost [127.0.0.1])
	by as.vix.com (Postfix) with ESMTP
	id 6AA2D379EF8; Sun, 23 Feb 2003 23:01:53 +0000 (GMT)
From: Paul Vixie <paul@vix.com>
To: Mark.Andrews@isc.org
Cc: "D. J. Bernstein" <djb@cr.yp.to>, ietf@ietf.org, iesg@ietf.org,
        namedroppers@ops.ietf.org
Subject: Re: update timing errors 
In-Reply-To: Message from Mark.Andrews@isc.org 
	of "Mon, 24 Feb 2003 08:28:07 +1100."
	<200302232128.h1NLS74U020848@drugs.dv.isc.org> 
X-Mailer: MH-E 7.2; nmh 1.0.4; GNU Emacs 21.2.1
Date: Sun, 23 Feb 2003 23:01:53 +0000
Message-Id: <20030223230153.6AA2D379EF8@as.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

ok mark, that's it.  no more replies are warranted.  if mr. bernstein
still misunderstands zone coherency, then someone who doesn't work for
ISC will have to take a turn trying to educate him.  we're done. --paul

ps. great answer btw.

re:

> X-Original-To: vixie@vix.com
> To: "D. J. Bernstein" <djb@cr.yp.to>
> Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
> From: Mark.Andrews@isc.org
> Subject: Re: update timing errors 
> Date: Mon, 24 Feb 2003 08:28:07 +1100
> Sender: owner-namedroppers@ops.ietf.org
> 
> 
> > Mark.Andrews@isc.org writes:
> > > If you never update the child then it is an *administrative* error.
> > 
> > Changing the serial number too early is also an administrative error.
> > Here's a summary of our three examples of administrative errors:
> > 
> >    1. Failing to update the parent serial number after updating the glue
> >       in all the child servers. As you keep pointing out, this error can
> >       cause problems with BIND 8: the data will be inconsistent until
> >       the serial number is updated.
> > 
> >    2. Failing to update the parent serial number after updating the glue
> >       in the parent master. This error can cause problems with BIND 9
> >       (and BIND 8, of course): the data will be inconsistent until the
> >       serial number is updated.
> > 
> >    3. Failing to update the data in the child master. This error can
> >       cause problems with BIND 9 (and BIND 8, of course): the data will
> >       be inconsistent until the child data is updated (and the serial
> >       numbers handled properly).
> > 
> > In every case, the administrator is violating RFC 1034 (as you have
> > admitted), and is creating a configuration that does not work properly
> > with most DNS software deployed in the real world.
> > 
> > You persist in drawing a completely unjustified line between the first
> > error and the other two errors. You claim that allowable administrative
> > action is defined by BIND 9---never mind what RFC 1034 says, and never
> > mind the rest of the installed base. You cycle endlessly between ``BIND
> > 9 is doing the Right Thing'' and ``BIND 9 handles that situation'' and
> > ``that situation is not actually an error,'' attempting to defend each
> > part of the BIND 9 religion by showing how it fits with the other parts.
> > The circularity is pathetic.
> > 
> > In situations where there's a difference between the software and the
> > spec---for example, actions that are prohibited by RFC 1034 even though
> > they work in the real world, or vice versa---one can reasonably discuss
> > whether the actions should be considered errors. But the above actions
> > do _not_ work and are _not_ allowed by the spec. If you want to support
> > them in BIND 9, fine, but you have no basis for demanding that the rest
> > of us support them too.
> 
> 	Changing the content of SECONDARY zones is outside of the
> 	actions specified by RFC 1034.  In fact RFC 1034 demands a
> 	"accurate" copy.  You can't have a "accurate" copy if it
> 	has been changed.
> 
> 	There are no timing issues if you have a "accurate" copy.
> 
> 	There is no such thing as changing the serial "too early".
> 
> 	It is the errors in BIND 4, BIND 8 and tinydns that introduce
> 	timing constraints that are not part of RFC 1034 and only
> 	affect servers that are serving both parent and child zones.
> 
> 	We have heard from at least three other independent developers
> 	that they preserve / preserved the copy of the child zone
> 	based on RFC 1034 requirement.
> 
> 	Maintaining consistancy between parent and child zones is
> 	a administrative responsability.  Even with automated
> 	assistance the changes are required to be applied to the
> 	PRIMARY not to the SECONDARY.  BIND 4, BIND 8 and tinydns
> 	violate the maintance model as a result of applying changes
> 	in the incorrect place directly leading to the situation where
> 	all the PRIMARY copies of the zones have the correct information
> 	but some of the SECONDARY "copies" don't.
> 
> 	There is no technical reason not to preserve the contents of
> 	the SECONDARY copies of the zone unaltered.  There are no
> 	negative effects from doing this.  There definitely are negative
> 	effects caused by changing the contents of SECONDARY copies.
> 
> 	All your complaints are based on your interpretation of RFC
> 	1034.  Your interpretation introduces timing issues which
> 	even your own software cannot meet without violating the
> 	requirement to change the serial number when you change the
> 	zone contents.
> 
> 	In addition to the pure AXFR issues.  IXFR depends upon the
> 	contents of the zone not being changed unilaterally on the
> 	SECONDARY.  Failure to preserve the contents will result
> 	in deltas not applying that should.  This should result in
> 	fallback to AXFR to get a upto date copy of the zone.  This
> 	will result in a AXFR style IXFR to done stream servers.
> 
> 	Mark
> 
> --
> Mark Andrews, Internet Software Consortium
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@isc.org
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-ietf@ietf.org  Sun Feb 23 19:25:13 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15781;
	Sun, 23 Feb 2003 19:25:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18n6Q0-0002Ba-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 19:24:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18n6Ox-0002AY-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 19:23:23 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15687
	for <ietf@ietf.org>; Sun, 23 Feb 2003 19:13:50 -0500 (EST)
Received: (qmail 72006 invoked by uid 1016); 24 Feb 2003 00:18:09 -0000
Date: 24 Feb 2003 00:18:09 -0000
Message-ID: <20030224001809.72005.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: update timing errors
References: <20030223091513.85299.qmail@cr.yp.to> <200302232128.h1NLS74U020848@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mark.Andrews@isc.org writes:
> Changing the content of SECONDARY zones is outside of the
> actions specified by RFC 1034.

Fact: Slaves _must_ discard records in some situations. A detailed
example appears in http://cr.yp.to/djbdns/axfr-notes.html#poison.
(There are many other counterexamples to your ``no reason'' claim.)

Fact: Slaves _do_ discard records in many situations. You claim that
this is ``wrong'' solely because it can break certain configurations.
You have admitted that RFC 1034 clearly prohibits those configurations.

> It is the errors in BIND 4, BIND 8 and tinydns that introduce
> timing constraints that are not part of RFC 1034

Fact: As you have already admitted, RFC 1034 _does_ impose these timing
constraints. As you have already admitted, RFC 1034 prohibits even the
slightest configuration inconsistency. In previous messages, you were
complaining about how severe the RFC 1034 consistency requirement is!

Fact: As above, your sole basis for calling the widespread BIND-8-etc.
behavior an ``error'' is that it doesn't work with your broken
configurations. Your sole basis for claiming that the configurations
aren't broken is _some_ DNS servers support them.

Fact: These broken configurations are going to continue to fail for the
foreseeable future. (As http://cr.yp.to/surveys/dns1.html shows, BIND 8
is more widely used than BIND 9.) It is essential for interoperability
that these broken configurations continue to be prohibited. Demanding
support for them would impose costs on at least two independent
implementations, without providing any benefits for the users.

Fact: Making the configurations work is a simple matter of updating the
parent---most importantly, the parent serial number---after (or at the
same time as) all the child servers are updated. This rule is easy for
administrators to follow.

> All your complaints are based on your interpretation of RFC 1034.

Fact: There are no relevant disputes about the interpretation of RFC
1034. When I pointed to the sections of RFC 1034 that you are violating,
you admitted your violations.

> change the serial number when you change the zone contents

Fact: That's part of what RFC 1034 requires. However, that's not even
close to a complete description of an RFC-1034-compliant glue-update
procedure. More importantly, it's not a complete description of a
glue-update procedure that works in practice.

> IXFR depends upon

Fact: IXFR is an optional protocol extension. It is entirely IXFR's
responsibility to maintain compatibility with the preexisting,
unextended, protocol. It is not the responsibility of the installed base
to change for the sake of new protocol options.

Fact: When a protocol extension causes failures with most of the
software deployed on the Internet, you can't safely use the extension
without waiting for a massive upgrade. Users are much happier with an
extension that, at comparable cost, avoids the failures and provides
the same benefits immediately. I have explained to you how to do this
in the case of IXFR.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Sun Feb 23 20:35:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17005;
	Sun, 23 Feb 2003 20:35:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18n7Xh-0003YW-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 20:36:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18n7XF-0003Xq-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 20:36:01 -0500
Received: from ccr.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16731;
	Sun, 23 Feb 2003 20:26:28 -0500 (EST)
Received: from ccr.org (localhost [127.0.0.1])
	by ccr.org (8.9.2/8.11.0) with ESMTP id UAA39348;
	Sun, 23 Feb 2003 20:30:19 -0500 (EST)
	(envelope-from mo@ccr.org)
Message-Id: <200302240130.UAA39348@ccr.org>
To: djb@cr.yp.to
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: your ongoing diatribe
Date: Sun, 23 Feb 2003 20:30:19 -0500
From: "Mike O'Dell" <mo@ccr.org>
Sender: owner-ietf@ietf.org
Precedence: bulk


Excuse me, sir, but I've enjoyed quite enough of your behavior

Your lack of genuine operating experience is transparent.  don't quote
	adoption numbers for your software - i'm talking about *you*
	having direct experience running very large name server systems
	with many tens of thousands of zones, both primary and secondary,
	or equivalently, working hand-in-glove with those who have

Your failure (nee unwillingness) to appreciate the large-scale
	consequences of your mathematical fantasy land is simply stunning

The fact the Real World doesn't care about the constraints you've constructed
	to make your world view viable doesn't seem to faze you

In particular, you don't appreciate the necessity of reasonable
	operational behavior in the presence of multiple
	administrative domains which cannot perform with
	perfect coordination

Then you have the audacity to describe those with a deep understanding
	of what it takes to make the Big-I Internet work at very
	large scale as "pathetic".

Frankly, sir, sit down. You have embarrassed yourself in this forum
	quite enough and have impeded the efforts of those working
	mightily to move things along in a constructive manner.

You seem to imagine this is some kind of debating society where you
	gain points by taking yet another turn at the microphone
	when your opponents have been worn down by arguing with a
	refractory surface.

It isn't a debating society, "rough consensus" goes not require unanimity
	and there is serious work to get done, so I ask again,

Sir, please sit down.

	I now return you to the previous screed,
	-mo




From owner-ietf@ietf.org  Sun Feb 23 23:04:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20340;
	Sun, 23 Feb 2003 23:04:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18n9sr-0001QJ-00
	for ietf-list@ran.ietf.org; Sun, 23 Feb 2003 23:06:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18n9s0-0001Pg-00
	for ietf@ran.ietf.org; Sun, 23 Feb 2003 23:05:36 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA20215
	for <ietf@ietf.org>; Sun, 23 Feb 2003 22:56:00 -0500 (EST)
Received: (qmail 47336 invoked by uid 1016); 24 Feb 2003 04:00:21 -0000
Date: 24 Feb 2003 04:00:21 -0000
Message-ID: <20030224040021.47335.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Poison in a zone
References: <20030223091513.85299.qmail@cr.yp.to> <200302232128.h1NLS74U020848@drugs.dv.isc.org> <20030224001809.72005.qmail@cr.yp.to> <200302240239.h1O2dAh00524@guava.araneus.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Andreas Gustafsson writes:
> D. J. Bernstein writes:
> > Fact: Slaves _must_ discard records in some situations.
> This claim has no basis in the standards.

Anti-poisoning rules are required for security. I'm not going to bother
addressing the irrelevant question of whether the de-facto standards in
DNS security can be deduced from the de-jure standards.

You have some anti-poisoning rules in BIND 9 (and BIND 8). We all know
that they're necessary: some records have to be discarded. Consequently,
any claim such as ``all records must be preserved'' is obviously wrong.
When religious rhetoric crashes into security, we all know who wins.

Yes or no: Does the specific attack described on my web page work
against BIND 9? I'll give you three days to issue a security release
before I send a message to bugtraq. Or are you using the defense stated
on my web page, discarding records on the client side of an AXFR?

> where the ISP is the *master* for the domains

Different situation, but same solution: discard all records outside the
source's bailiwick. End of problem.

> more discriminate anti-spoofing rules

Namely? Exactly what would you suggest in place of the de-facto-standard
bailiwick rule? (You realize, of course, that deploying a new rule would
take time.)

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Mon Feb 24 02:30:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03762;
	Mon, 24 Feb 2003 02:30:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nD2K-00044Q-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 02:28:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nD1Z-00043q-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 02:27:41 -0500
Received: from gorilla.mchh.siemens.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03587
	for <ietf@ietf.org>; Mon, 24 Feb 2003 02:18:04 -0500 (EST)
Received: from blues.mchh.siemens.de ([139.21.204.206])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id IAA24687;
	Mon, 24 Feb 2003 08:21:55 +0100 (MET)
Received: from mchh273e.demchh201e.icn.siemens.de (mchh273e.mchh.siemens.de [139.21.200.83])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id IAA15338;
	Mon, 24 Feb 2003 08:21:25 +0100 (MET)
Received: by mchh273e.mchh.siemens.de with Internet Mail Service (5.5.2656.59)
	id <1JB58D5H>; Mon, 24 Feb 2003 08:21:05 +0100
Message-ID: <BE684E2C997AD51199530002A56B207904CC4F27@mchh2a1e.mchh.siemens.de>
From: Brandner Rudolf <rudolf.brandner@siemens.com>
To: "'Christian Huitema'" <huitema@windows.microsoft.com>
Cc: "'Paul Vixie'" <paul@vix.com>, ietf@ietf.org
Subject: RE: Autoreply from Internet Draft Submission Manager
Date: Mon, 24 Feb 2003 08:21:04 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi all,

I've got it, too. Looks like the autoreply is set somehow wrong.

Rudi

> -----Original Message-----
> From: Christian Huitema [mailto:huitema@windows.microsoft.com]
> Sent: Sonntag, 23. Februar 2003 00:26
> To: ietf@ietf.org
> Subject: FW: Autoreply from Internet Draft Submission Manager
> 
> 
> This automatic reply from the Internet Draft submission would 
> have us believe that the holiday season is still going on...
> 
> ________________________________
> 
> From: Internet Draft Submission Manager [mailto:ietfauto@ietf.org]
> Sent: Sat 2/22/2003 1:19 PM
> To: Christian Huitema
> Subject: Autoreply from Internet Draft Submission Manager
> 
> 
> 
> Hello,
> 
> This message is being sent to acknowledge receipt of your submission
> or message to internet-drafts@ietf.org
> 
> The I-D administrator will be out of the office from December 
> 23rd until Monday,
> January 6, 2003. All submissions will be processed.
> 
> Thank you. We appreciate your understanding and patience.
> 
> Have a wonderful and joyous holiday season.
> 
> Internet-Drafts Administrator
> 
> 
> 



From owner-ietf@ietf.org  Mon Feb 24 14:08:53 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22903;
	Mon, 24 Feb 2003 14:08:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nNyl-0006ww-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 14:09:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nNyg-0006uz-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 14:09:26 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22619;
	Mon, 24 Feb 2003 13:59:42 -0500 (EST)
Received: from [192.168.1.4] (askvoll.hjemme.alvestrand.no [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5B346622BB; Mon, 24 Feb 2003 20:03:35 +0100 (CET)
Date: Mon, 24 Feb 2003 20:03:35 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Respect for others (RE: your ongoing diatribe)
Message-ID: <2151130000.1046113415@askvoll.hjemme.alvestrand.no>
In-Reply-To: <CE541259607DE94CA2A23816FB49F4A310FF8E@vhqpostal6.verisign.com>
References:  <CE541259607DE94CA2A23816FB49F4A310FF8E@vhqpostal6.verisign.com>
X-Mailer: Mulberry/2.2.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA22903

Since Phil claims that this behaviour comes "from the top down", and it's 
hard to find anyone who can be "the top" above me....

I find the behaviour Phil Hallam-Baker describes below unacceptable.

At times, a quickly-tossed-off "I know this is false, but I don't have the 
time to show you the proof" is acceptable as a placeholder until time can 
be made; at times, an "I have explained this problem to you twentyseven 
times, and you still don't agree with me" is nothing more than the simple 
truth, and we have to recognize the underlying disagreement.

But in general, asking the IETF to accept consensus on an unsubstantiated 
objection is no more acceptable than asking the IETF to accept consensus on 
an undocumented proposal.

                        Harald


--On søndag, februar 23, 2003 19:21:08 -0800 "Hallam-Baker, Phillip" 
<pbaker@verisign.com> wrote:

> I think that the underlying problem here is lack of respect. Frankly I
> don't much care about the technical issues someone is putting forward
> when they are behaving like a shouting head from a sunday talk show.
>
> While Prof Bernsteins posts and general behaviour shows a total lack of
> respect for others I don't think the problem is unique to members of the
> crazy gang.
>
> One of the issues I have with the IETF generally is that the feedback I
> frequently get back on ideas is 'if you understood the problem you would
> know why your proposal is stupid', followed by a blank refusal to cite
> specifics. This is an argument strategy that will be familliar to the
> readers of Joseph Heller.
>
> I am not talking about random bar room conversations here, I am talking
> about longstanding IESG and IAB members. If I get treated that way after
> ten years of involvement with network protocols, how does the graduate
> student who comes to her first IETF get treated?
>
> The point is that this type of behaviour is comming from the top down.
>
>
> 		Phill





From owner-ietf@ietf.org  Mon Feb 24 14:59:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24428;
	Mon, 24 Feb 2003 14:59:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nOoR-0005JH-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 15:02:55 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nOnM-0005G9-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 15:01:48 -0500
Received: from tnt.isi.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24217
	for <ietf@ietf.org>; Mon, 24 Feb 2003 14:52:03 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id h1OJttb01178;
	Mon, 24 Feb 2003 11:55:55 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id TAA08921;
	Mon, 24 Feb 2003 19:55:54 GMT
Date: Mon, 24 Feb 2003 19:55:54 GMT
Message-Id: <200302241955.TAA08921@gra.isi.edu>
To: m-shimada@ab.jp.nec.com
Subject: Re: Protocl Status
Cc: ietf@ietf.org, braden@ISI.EDU, rfc-editor@rfc-editor.org
X-Sun-Charset: US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


  *> 
  *> Hi,
  *> 
  *> I have a following question. Please someone teach me.
  *> 
  *> RFC2400(INTERNET OFFICIAL PROTOCOL STANDARDS) describes a 
  *> status like Req or Rec for each Protocol but RFC2500 does NOT 
  *> describe status. RFC2500 obsoletes RFC2400.
  *> What RFC describes a status for each protocol?
  *> Where can I find status description for each protocol? 
  *> 
  *> Thanks,
  *> Masao
  *> 
  *> 

Masao,

You probably understand this, but RFC 2400 was obsoleted by RFC 2500,
which was obsoleted by RFC 2600, which was obsoleted by RFC 2700, which
was obsoleted by RFC 2800, which was obsoleted by RFC 2900, which was
obsoleted by RFC 3000, which was obsoleted by RFC 3300.  And the series
stretches backwards from 2400...  The most recent Internet Official
Protocols Standards list, also known as STD1, is currently RFC 3300.
Furthermore, the current information is on the RFC Editor web page at
http://www.rfc-editor.org/rfcxx00.html.

However, as you noticed, there was a column of information marked
"Status" that disappeared after RFC 2400.  To understand this
you need to understand some history.  Today's procedures for
setting and documenting Internet standards did not just spring
magically into existence, they evolved over 20 years, starting from
the time when the Internet was simply an experiment.

The "Status" attribute listed in RFC 2400 and earlier was actually a
"requirement level" in the terminology of RFC 2026 (which defines the
standards process.)  In the early days, as the Internet was expanding
and becoming commercial, the IAB faced the problem of documenting the
protocol suite so that vendors could produce products.  In 1988, the US
government body (FRICC) that was sort of overseeing the Internet
"asked" the IAB to create an official list of standard Internet
protocols.  ("Standard" was somewhat fuzzily defined in those days...
the standards level for a spec was what the IAB said it was.)  Jon
Postel created the list and published it as RFC 1083.

Obviously a vendor did not need to implement every protocol in RFC
1083, and that had to be indicated somehow.  Jon's solution was to
attach a requirement level or "status" -- "required", "recommended",
"elective", or "not recommended" -- to each protocol listed in RFC 1083.

However, it rapidly become clear that reality is much more complex
than can be captured in two bits of status information.  In fact,
around that time the IETF was turning out 214 pages of finely wrought
prose on the requirements for Internet protocol software in hosts
(1122, 1123), and later the RFC 1812 paper weight did the same for
routers.  However, Jon was a very determined fellow, and he continued
to apply the Status fields in successors to RFC 1083 despite the fact
that the information it contained was of value that increasingly
approached zero.

This reality was finally recognized by the RFC Editor in 1999, and
subsequent editions of the Official Protocols RFCs, starting with RFC
2500, dropped the Status field.

I hope this explanation is helpful.

Bob Braden for the RFC Editor


  *> part of RFC2400 is as follows
  *> --------------------------------------------------------------------
  *> Internet Architecture Board Standards Track                [Page 20]
  *> 
  *> RFC 2400                   Internet Standards         September 1998
  *> 
  *> 
  *> 6.2.  Standard Protocols
  *> 
  *> Protocol   Name                                  Status    RFC STD *
  *> ========   ===================================== ======== ==== === =
  *> --------   Internet Official Protocol Standards  Req      2400   1
  *> --------   Assigned Numbers                      Req      1700   2
  *> --------   Host Requirements - Communications    Req      1122   3
  *> --------   Host Requirements - Applications      Req      1123   3
  *> IP         Internet Protocol                     Req       791   5
  *>             as amended by:--------
  *> --------     IP Subnet Extension                 Req       950   5
  *> --------     IP Broadcast Datagrams              Req       919   5
  *> --------     IP Broadcast Datagrams with Subnets Req       922   5
  *> ICMP       Internet Control Message Protocol     Req       792   5
  *> IGMP       Internet Group Multicast Protocol     Rec      1112   5
  *> UDP        User Datagram Protocol                Rec       768   6
  *> TCP        Transmission Control Protocol         Rec       793   7
  *> TELNET     Telnet Protocol                       Rec   854,855   8
  *> FTP        File Transfer Protocol                Rec       959   9
  *> SMTP       Simple Mail Transfer Protocol         Rec       821  10
  *> 


----- End Included Message -----




From owner-ietf@ietf.org  Mon Feb 24 15:32:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25488;
	Mon, 24 Feb 2003 15:32:13 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nPJy-0007hw-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 15:35:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nPJn-0007gM-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 15:35:19 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25350;
	Mon, 24 Feb 2003 15:25:34 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18nPDI-0003cV-00; Mon, 24 Feb 2003 20:28:36 +0000
Date: Mon, 24 Feb 2003 20:28:32 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, "" <ietf@ietf.org>,
        "" <iesg@ietf.org>, "" <namedroppers@ops.ietf.org>
Subject: Re: Respect for others (RE: your ongoing diatribe)
In-Reply-To: <2151130000.1046113415@askvoll.hjemme.alvestrand.no>
Message-ID: <Pine.GSO.4.50.0302242026110.21820-100000@artemis.ee.surrey.ac.uk>
References: <CE541259607DE94CA2A23816FB49F4A310FF8E@vhqpostal6.verisign.com>
 <2151130000.1046113415@askvoll.hjemme.alvestrand.no>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-102.5 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,REFERENCES,
	      SPAM_PHRASE_00_01,USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18nPDI-0003cV-00*H68cB32Qijk* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Mon, 24 Feb 2003, Harald Tveit Alvestrand wrote:

> Since Phil claims that this behaviour comes "from the top down", and it's
> hard to find anyone who can be "the top" above me....

you're admin of namedroppers now?

L.

and the longest-serving member of the IESG is...?

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>



From owner-ietf@ietf.org  Mon Feb 24 17:24:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28631;
	Mon, 24 Feb 2003 17:24:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nR1S-0003dA-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 17:24:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nR0i-0003bY-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 17:23:44 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA28377
	for <ietf@ietf.org>; Mon, 24 Feb 2003 17:13:56 -0500 (EST)
Received: (qmail 93063 invoked by uid 1016); 24 Feb 2003 22:18:18 -0000
Date: 24 Feb 2003 22:18:18 -0000
Message-ID: <20030224221818.93062.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: your ongoing diatribe
References: <200302240130.UAA39348@ccr.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Mike O'Dell writes:
> cannot perform with perfect coordination

RFC 1034 requires perfect coordination. However, I've been pointing out
that a much looser glue-update procedure works just fine:

   (1) Change the data in the child zone on the child master.
   (2) Once #1 is done: Change the child serial number.
   (3) Once #2 is done: Copy the new data to all the child slaves, for
       example by waiting for the slaves to pull the data through AXFR.
   (4) Change the data in the parent zone on the parent master.
   (5) Once #3 and #4 are done: Change the parent serial number.
   (6) Once #5 is done: Copy the new data to all the parent slaves, for
       example by waiting for the slaves to pull the data through AXFR.

This guarantees a successful update with all of today's DNS software.
For example, the update will succeed if the child administrator does #1,
#2, #3 and then tells the parent administrator to do #4, #5, #6. Easy!

If you violate the timing constraints---for example, if you change the
parent serial number too early---then the update may fail. For example,
breaking the #3<=#5 rule can cause failures with BIND 8, and breaking
the #4<=#5 rule can cause failures with BIND 8 or BIND 9. Solution:
Don't break the rules!

The BIND company has been drawing a completely unjustified line between
the #3<=#5 rule and the other rules. They're demanding that we go to a
lot of effort to allow #5<#3 because BIND 9 does. How is this supposed
to benefit the administrators?

Even if we started on this massive upgrade, #5<#3 would remain unsafe
for the foreseeable future. Not only is there a huge BIND 8 installed
base, but many OS distributors are deliberately avoiding BIND 9. So
administrators would have to continue following the #3<=#5 rule for
the foreseeable future. The BIND company is simply trying to make extra
work for competing DNS implementations.

There's a long history of the BIND company introducing interoperability
problems: their multiple-answers AXFR format, for example, and their
failure to handle NODATA responses to IXFR. They try to blame the other
side for these failures, even when BIND is clearly violating RFC 1034
(as in the IXFR case) and could easily have avoided the failures (as in
the multiple-answers and IXFR cases). They use these failures to market
the latest version of BIND: if you change to BIND on the other side,
everything will work again! This is reprehensible.

> don't quote adoption numbers for your software

Why not? You talk about ``very large name server systems'' and
``large-scale consequences'' and ``the Real World'' and ``the Big-I
Internet,'' and you expect me not to mention that tinydns is being used
by seven of the largest .com hosting companies on the Internet?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Mon Feb 24 19:07:41 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00899;
	Mon, 24 Feb 2003 19:07:41 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nSe6-0007Iu-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 19:08:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nSd7-0007Ga-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 19:07:29 -0500
Received: from web14712.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA00764
	for <ietf@ietf.org>; Mon, 24 Feb 2003 18:57:43 -0500 (EST)
Message-ID: <20030225000135.97511.qmail@web14712.mail.yahoo.com>
Received: from [64.160.223.11] by web14712.mail.yahoo.com via HTTP; Mon, 24 Feb 2003 16:01:35 PST
Date: Mon, 24 Feb 2003 16:01:35 -0800 (PST)
From: Sean Dorman <sean_dorman@yahoo.com>
Subject: Re: Respect for others (RE: your ongoing diatribe)
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
In-Reply-To: <2151130000.1046113415@askvoll.hjemme.alvestrand.no>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-711066112-1046131295=:97356"
Sender: owner-ietf@ietf.org
Precedence: bulk

--0-711066112-1046131295=:97356
Content-Type: text/plain; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA00765
Content-Transfer-Encoding: quoted-printable


It doesn't necessarily come from the top down, just from those who lack t=
he sensibility to provide a concise and answer, followed by useful inform=
ation & examples, those who are immature & full of themselves, and those =
who do not have enough time to formulate their usual BS that no one wants=
 to hear...
Sean Dorman
 Harald Tveit Alvestrand <harald@alvestrand.no> wrote:Since Phil claims t=
hat this behaviour comes "from the top down", and it's=20
hard to find anyone who can be "the top" above me....

I find the behaviour Phil Hallam-Baker describes below unacceptable.

At times, a quickly-tossed-off "I know this is false, but I don't have th=
e=20
time to show you the proof" is acceptable as a placeholder until time can=
=20
be made; at times, an "I have explained this problem to you twentyseven=20
times, and you still don't agree with me" is nothing more than the simple=
=20
truth, and we have to recognize the underlying disagreement.

But in general, asking the IETF to accept consensus on an unsubstantiated=
=20
objection is no more acceptable than asking the IETF to accept consensus =
on=20
an undocumented proposal.

Harald


--On s=F8ndag, februar 23, 2003 19:21:08 -0800 "Hallam-Baker, Phillip"=20

wrote:

> I think that the underlying problem here is lack of respect. Frankly I
> don't much care about the technical issues someone is putting forward
> when they are behaving like a shouting head from a sunday talk show.
>
> While Prof Bernsteins posts and general behaviour shows a total lack of
> respect for others I don't think the problem is unique to members of th=
e
> crazy gang.
>
> One of the issues I have with the IETF generally is that the feedback I
> frequently get back on ideas is 'if you understood the problem you woul=
d
> know why your proposal is stupid', followed by a blank refusal to cite
> specifics. This is an argument strategy that will be familliar to the
> readers of Joseph Heller.
>
> I am not talking about random bar room conversations here, I am talking
> about longstanding IESG and IAB members. If I get treated that way afte=
r
> ten years of involvement with network protocols, how does the graduate
> student who comes to her first IETF get treated?
>
> The point is that this type of behaviour is comming from the top down.
>
>
> Phill





---------------------------------
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, and more
--0-711066112-1046131295=:97356
Content-Type: text/html; charset=us-ascii
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA00765
Content-Transfer-Encoding: quoted-printable

<P>It doesn't necessarily come from the top down, just from those who lac=
k the sensibility to provide a concise and answer, followed by useful inf=
ormation &amp; examples, those who are immature &amp; full of themselves,=
 and those who do not have enough time to formulate their usual BS that n=
o one wants to hear...
<P>Sean Dorman
<P>&nbsp;<B><I>Harald Tveit Alvestrand &lt;harald@alvestrand.no&gt;</I></=
B> wrote:
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1=
010ff 2px solid">Since Phil claims that this behaviour comes "from the to=
p down", and it's <BR>hard to find anyone who can be "the top" above me..=
..<BR><BR>I find the behaviour Phil Hallam-Baker describes below unaccept=
able.<BR><BR>At times, a quickly-tossed-off "I know this is false, but I =
don't have the <BR>time to show you the proof" is acceptable as a placeho=
lder until time can <BR>be made; at times, an "I have explained this prob=
lem to you twentyseven <BR>times, and you still don't agree with me" is n=
othing more than the simple <BR>truth, and we have to recognize the under=
lying disagreement.<BR><BR>But in general, asking the IETF to accept cons=
ensus on an unsubstantiated <BR>objection is no more acceptable than aski=
ng the IETF to accept consensus on <BR>an undocumented proposal.<BR><BR>H=
arald<BR><BR><BR>--On s=F8ndag, februar 23, 2003 19:21:08 -0800 "Hallam-B=
aker, Phillip" <BR><PBAKER@VERISIGN.COM>wrote:<BR><BR>&gt; I think that  =
the underlying problem here is lack of respect. Frankly I<BR>&gt; don't m=
uch care about the technical issues someone is putting forward<BR>&gt; wh=
en they are behaving like a shouting head from a sunday talk show.<BR>&gt=
;<BR>&gt; While Prof Bernsteins posts and general behaviour shows a total=
 lack of<BR>&gt; respect for others I don't think the problem is unique t=
o members of the<BR>&gt; crazy gang.<BR>&gt;<BR>&gt; One of the issues I =
have with the IETF generally is that the feedback I<BR>&gt; frequently ge=
t back on ideas is 'if you understood the problem you would<BR>&gt; know =
why your proposal is stupid', followed by a blank refusal to cite<BR>&gt;=
 specifics. This is an argument strategy that will be familliar to the<BR=
>&gt; readers of Joseph Heller.<BR>&gt;<BR>&gt; I am not talking about ra=
ndom bar room conversations here, I am talking<BR>&gt; about longstanding=
 IESG and IAB members. If I get treated that way after<BR>&gt; ten years =
of involvement with network protocols, how does the graduate<BR>&gt; stud=
ent who comes to her first IETF get treated?<BR>&gt;<BR>&gt; The point is=
 that this type of behaviour is comming from the top down.<BR>&gt;<BR>&gt=
;<BR>&gt; Phill<BR><BR><BR></BLOCKQUOTE><p><br><hr size=3D1>Do you Yahoo!=
?<br>
<a href=3D"http://rd.yahoo.com/finance/mailtagline/*http://taxes.yahoo.co=
m/">Yahoo! Tax Center</a> - forms, calculators, tips, and more
--0-711066112-1046131295=:97356--



From owner-ietf@ietf.org  Mon Feb 24 19:59:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01888;
	Mon, 24 Feb 2003 19:59:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nTOY-0000an-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 19:56:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nTOD-0000Z9-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 19:56:09 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01668
	for <ietf@ietf.org>; Mon, 24 Feb 2003 19:46:22 -0500 (EST)
Received: (qmail 72048 invoked by uid 1016); 25 Feb 2003 00:50:42 -0000
Date: 25 Feb 2003 00:50:42 -0000
Message-ID: <20030225005042.72047.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org, iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Poison in a zone
References: <20030223091513.85299.qmail@cr.yp.to> <200302232128.h1NLS74U020848@drugs.dv.isc.org> <20030224001809.72005.qmail@cr.yp.to> <200302240239.h1O2dAh00524@guava.araneus.fi> <20030224040021.47335.qmail@cr.yp.to> <200302242340.h1ONeur00731@guava.araneus.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

A moment ago we were being told how vitally important it was for AXFR
clients to preserve all records received under all circumstances:

   * ``An ACURATE [sic] copy of the zone is ESSENTIAL'';
   * ``A modified zone is NOT a [sic] ACURATE [sic] copy. It's not
     even a copy. It is a derived work'';
   * ``IXFR depends upon the contents of the zone not being changed
     unilaterally on the SECONDARY'';
   * ``Bernstein still misunderstands zone coherency''; etc.

This rhetoric is supposed to convince you that the majority of AXFR
clients (BIND 8 et al.) are doing something wrong by discarding parent
glue records when they have the authoritative child records.

But now Gustafsson admits that the BIND 9 AXFR client doesn't follow
the ``zone coherency'' religion. It deliberately discards some kinds of
records! It isn't making a perfect copy of the zone! It's breaking IXFR!
Here's the quote: ``BIND 9 ... will discard [these] records whether they
are loaded from a master file or received as part of a zone transfer.''

To summarize: Not only is the BIND company (1) fraudulently labelling
its religion as a ``clarification'' and (2) fraudulently claiming
``consensus'' on the religion over the objections of several people,
but it is also (3) deliberately disobeying its own commandments.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Mon Feb 24 21:38:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03840;
	Mon, 24 Feb 2003 21:38:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nV0E-0003nW-00
	for ietf-list@ran.ietf.org; Mon, 24 Feb 2003 21:39:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nUzH-0003lo-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 21:38:31 -0500
Received: from VL-MS-MR004.sc1.videotron.ca (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03300
	for <ietf@ietf.org>; Mon, 24 Feb 2003 21:28:42 -0500 (EST)
Received: from leputer ([24.200.34.38]) by VL-MS-MR004.sc1.videotron.ca
 (iPlanet Messaging Server 5.2 HotFix 1.10 (built Jan 23 2003))
 with SMTP id <0HAU008U3F3UMS@VL-MS-MR004.sc1.videotron.ca> for ietf@ietf.org;
 Mon, 24 Feb 2003 21:33:31 -0500 (EST)
Date: Mon, 24 Feb 2003 21:30:55 -0500
From: Michael <KungFuMan@videotron.ca>
Subject: Re: Poison in a zone
To: ietf@ietf.org
Message-id: <001e01c2dc75$ecb8e5e0$1900000a@leputer>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20030223091513.85299.qmail@cr.yp.to>
 <200302232128.h1NLS74U020848@drugs.dv.isc.org>
 <20030224001809.72005.qmail@cr.yp.to>
 <200302240239.h1O2dAh00524@guava.araneus.fi>
 <20030224040021.47335.qmail@cr.yp.to>
 <200302242340.h1ONeur00731@guava.araneus.fi>
 <20030225005042.72047.qmail@cr.yp.to>
Content-Transfer-Encoding: 7BIT
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

That Bernstein is definitly on Bind's case... ;) 

----- Original Message ----- 
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <ietf@ietf.org>; <iesg@ietf.org>; <namedroppers@ops.ietf.org>
Sent: Monday, February 24, 2003 7:50 PM
Subject: Re: Poison in a zone


> A moment ago we were being told how vitally important it was for AXFR
> clients to preserve all records received under all circumstances:
> 
>    * ``An ACURATE [sic] copy of the zone is ESSENTIAL'';
>    * ``A modified zone is NOT a [sic] ACURATE [sic] copy. It's not
>      even a copy. It is a derived work'';
>    * ``IXFR depends upon the contents of the zone not being changed
>      unilaterally on the SECONDARY'';
>    * ``Bernstein still misunderstands zone coherency''; etc.
> 
> This rhetoric is supposed to convince you that the majority of AXFR
> clients (BIND 8 et al.) are doing something wrong by discarding parent
> glue records when they have the authoritative child records.
> 
> But now Gustafsson admits that the BIND 9 AXFR client doesn't follow
> the ``zone coherency'' religion. It deliberately discards some kinds of
> records! It isn't making a perfect copy of the zone! It's breaking IXFR!
> Here's the quote: ``BIND 9 ... will discard [these] records whether they
> are loaded from a master file or received as part of a zone transfer.''
> 
> To summarize: Not only is the BIND company (1) fraudulently labelling
> its religion as a ``clarification'' and (2) fraudulently claiming
> ``consensus'' on the religion over the objections of several people,
> but it is also (3) deliberately disobeying its own commandments.
> 
> ---D. J. Bernstein, Associate Professor, Department of Mathematics,
> Statistics, and Computer Science, University of Illinois at Chicago
> 



From owner-ietf@ietf.org  Tue Feb 25 13:12:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09156;
	Tue, 25 Feb 2003 13:12:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18njVK-0003hf-00
	for ietf-list@ran.ietf.org; Tue, 25 Feb 2003 13:08:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18njV7-0003dm-00
	for ietf@ran.ietf.org; Tue, 25 Feb 2003 13:08:21 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08625;
	Tue, 25 Feb 2003 12:58:22 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA07675;
	Tue, 25 Feb 2003 10:01:32 -0800
Date: Tue, 25 Feb 2003 09:59:49 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1828675014.20030225095949@brandenburg.com>
To: "Eric Burger" <eburger@snowshore.com>
CC: "John C Klensin" <john-ietf@jck.com>, ned.freed@mrochek.com,
        "Pete Resnick" <presnick@qualcomm.com>, <ietf@ietf.org>,
        <iesg@ietf.org>, "IETF LEMONADE (E-mail)" <um@snowshore.com>
Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to support  diverse service environments (lemonade)
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
References: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

Thursday, January 30, 2003, 10:05:11 AM, you wrote:
EB> Executive Summary: Accept John's second proposal.  That is,
EB> take the charter as is, and insert a May 2003 deliverable of
EB> "lemonade Architecture, IESG and IETF Review, and Possible
EB> Rechartering".

I've waited to comment, because I was hoping to achieve some insight
that would allow a more directly constructive contribution. Alas, all
that has happened is time passing. Perhaps that is indicative of
something worth heeding by the WG...

With considerable regret, I find myself having to offer the following:

I believe Eric's suggestion is an excellent way to ensure that the
working group takes a long time, and is unproductive at the end of it.

        At base, the charter does not tell me what concrete problem this
        working group is solving or what use the output will be.

Here are the salient bits of text, from the opening paragraph of the
proposed charter -- and remember that the opening paragraph is
circulated independently, as the summary of the working group; therefore
it needs to summarize the problem and summarize the utility of the
output, if not also summarizing what will be done:

     "...facilitate operation in environments which use Internet-based
     technologies but which have link characteristics, device
     characteristics, or service environments that are significantly
     different from those common on the Internet..."

Excuse me, but I have not idea what this language means, and it does not
help that I was involved in the early lemonade discussions.  And, by the
way, I also do not know what link characteristics are "common" on the
Internet, what with FDDI, 10Mb ether, 802.11, cell phones, etc.,
nevermind not knowing what the new and different link characteristics
are.

So if the quoted text is supposed to refer to particular transmission
behaviors, it needs to state them clearly, and it should state what is
deficient in the existing set of specifications.

     "A primary goal of this work is to ensure that those profiles and
     enhancements continue to interoperate with the existing Internet
     email protocols in use on the Internet, so that these environments
     and more traditional Internet users have access to a seamless
     service."

No doubt I am misinterpreting this, but it sure sounds as if the goal is
to create some sort of new email service and try to make sure it can be
gatewayed to existing Internet email services?

(By the way, anyone seeking to define a gatewaying service should heed
the stellar history in the IMPP working group.)
     
So...

For this effort to be productive, the charter must be much, much more
clear and precise about the concrete, technical or operational problems
that exist and must give a concrete, constrained description of what is
going to be done to solve them.  And it must do this in simple, direct,
specific language.

Honest, I would offer some such language, but I have not succeeded at
figuring out what problems the group intends to solve or should solve.
        
d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.866-358-5301




From owner-ietf@ietf.org  Tue Feb 25 14:44:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12206;
	Tue, 25 Feb 2003 14:44:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nl1A-0003OF-00
	for ietf-list@ran.ietf.org; Tue, 25 Feb 2003 14:45:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nl0z-0003L0-00
	for ietf@ran.ietf.org; Tue, 25 Feb 2003 14:45:21 -0500
Received: from ithilien.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11931;
	Tue, 25 Feb 2003 14:35:22 -0500 (EST)
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h1PJd6YE010593;
	Tue, 25 Feb 2003 11:39:07 -0800 (PST)
Received: from CAMITLOAN6.qualcomm.com (camitloan6.qualcomm.com [129.46.225.112])
	by neophyte.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h1PJd0sd014887;
	Tue, 25 Feb 2003 11:39:01 -0800 (PST)
Message-Id: <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com>
X-Sender: hardie@mage.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 25 Feb 2003 11:37:10 -0800
To: Dave Crocker <dcrocker@brandenburg.com>,
        "Eric Burger" <eburger@snowshore.com>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to
  support  diverse service environments (lemonade)
Cc: "John C Klensin" <john-ietf@jck.com>, ned.freed@mrochek.com,
        "Pete Resnick" <presnick@qualcomm.com>, <ietf@ietf.org>,
        <iesg@ietf.org>, "IETF LEMONADE (E-mail)" <um@snowshore.com>
In-Reply-To: <1828675014.20030225095949@brandenburg.com>
References: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
 <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

Hi Dave,
         Some comments in-line.

At 09:59 AM 2/25/2003 -0800, Dave Crocker wrote:
>Folks,
>
>Thursday, January 30, 2003, 10:05:11 AM, you wrote:
>EB> Executive Summary: Accept John's second proposal.  That is,
>EB> take the charter as is, and insert a May 2003 deliverable of
>EB> "lemonade Architecture, IESG and IETF Review, and Possible
>EB> Rechartering".
>
>I've waited to comment, because I was hoping to achieve some insight
>that would allow a more directly constructive contribution. Alas, all
>that has happened is time passing. Perhaps that is indicative of
>something worth heeding by the WG...
>
>With considerable regret, I find myself having to offer the following:
>
>I believe Eric's suggestion is an excellent way to ensure that the
>working group takes a long time, and is unproductive at the end of it.
>
>         At base, the charter does not tell me what concrete problem this
>         working group is solving or what use the output will be.
>
>Here are the salient bits of text, from the opening paragraph of the
>proposed charter -- and remember that the opening paragraph is
>circulated independently, as the summary of the working group; therefore
>it needs to summarize the problem and summarize the utility of the
>output, if not also summarizing what will be done:
>
>      "...facilitate operation in environments which use Internet-based
>      technologies but which have link characteristics, device
>      characteristics, or service environments that are significantly
>      different from those common on the Internet..."


I think I contributed this text during a previous round of charter discussions;
sorry that it remains unclear.   From my point of view, the basic
problem here is that there are a set of services which are being
contemplated or deployed in specific environments which are based on
IETF protocols but do not interoperate with them, either well or at all.
The list you saw above:  link characteristics, device characteristics,
or service environments are the differences cited by those operating
those service environments as reasons for wanting "profiles" of
IETF protocols that meet their needs.  From my point of view,
we need to encourage them to do the protocol work in a way that
maintains interoperability with the core IETF protocols.  Hence
this language:

>      "A primary goal of this work is to ensure that those profiles and
>      enhancements continue to interoperate with the existing Internet
>      email protocols in use on the Internet, so that these environments
>      and more traditional Internet users have access to a seamless
>      service."
>
>No doubt I am misinterpreting this, but it sure sounds as if the goal is
>to create some sort of new email service and try to make sure it can be
>gatewayed to existing Internet email services?

Actually, avoiding the need to gateway between services is one of
my own goals for this work.  As it stands, some of those developing
these extensions are presuming that they will be able to handle
any interoperability problem with a gateway that shifts between their
version and the big-I Internet version.   The intent of "seamless service"
was, I believe, trying to get that message across:  you should not have
to have independent application layer protocols because you have
different service environments.  Better text welcome, as always.
I personally believe that you may, however, have to describe how to
use a set of protocols in an interoperable way when there are different
service environments involved.  In so doing, you may find some
part of the set which needs update or extension.


>So...
>
>For this effort to be productive, the charter must be much, much more
>clear and precise about the concrete, technical or operational problems
>that exist and must give a concrete, constrained description of what is
>going to be done to solve them.  And it must do this in simple, direct,
>specific language.

While I would welcome this, we also have to be practical about
the scale of things we put into the charter.  I think John's proposal
was to make this an early work item, so that later work can
be more focused about the problems which give rise to
these profiles of IETF messaging standards and what we can
do solve them in an interoperable way.  I believe that knowing the
non-interoperable profiles exist is enough to identify the need
to go through that part of the exercise.
                         regards,
                                 Ted Hardie





From owner-ietf@ietf.org  Tue Feb 25 15:57:42 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15783;
	Tue, 25 Feb 2003 15:57:42 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nm9n-0005Is-00
	for ietf-list@ran.ietf.org; Tue, 25 Feb 2003 15:58:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nm9X-0005Fi-00
	for ietf@ran.ietf.org; Tue, 25 Feb 2003 15:58:15 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15407;
	Tue, 25 Feb 2003 15:48:13 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id MAA16887;
	Tue, 25 Feb 2003 12:51:40 -0800
Date: Tue, 25 Feb 2003 12:51:38 -0800
From: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <10518983707.20030225125138@brandenburg.com>
To: Ted Hardie <hardie@qualcomm.com>
CC: "Eric Burger" <eburger@snowshore.com>,
        "John C Klensin" <john-ietf@jck.com>, <ned.freed@mrochek.com>,
        "Pete Resnick" <presnick@qualcomm.com>, <ietf@ietf.org>,
        <iesg@ietf.org>, "IETF LEMONADE (E-mail)" <um@snowshore.com>
Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to  support  diverse service environments (lemonade)
In-Reply-To: <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com>
References: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
 <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
 <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

First of all, I must apologize. Sure enough, I was looking at an older
version of the charter, in spite of having tried to avoid that error.
The versions that I had seen listed a couple of specifics, in the task
list portion, but it was only partial and the overall document seemed to
me to leave blind cliffs over which a WG could easily drive.

The current version lists specific actions that are clear and concise,
except perhaps the one about gatewaying to other services (more on that
inline)

I gather that the IAB is frankly dictating the current wording of the
opening paragraph. I am seriously dismayed to hear that. From an offline
exchange, Ned mentions a desire to have the paragraph include something
like "link characteristics of concern are those of high latency and low
bandwidth, the device characteristics are limited memory and processing
power, and the service environments are environments are MMS/WAP." I
very heartily concur. In fact it is exactly what I think is missing.

Keeping the IAB happy is always important, but I do not believe it
should result in a working group charter -- and especially not an
opening paragraph -- that is more obscure. However the fact that the
remainder of the charter is so specific moves my concern from immediate
and strong, to relatively theoretical.

Still if there is a way to enhance the opening paragraph, it really
would be nice. Something like:

      Internet mail devices often operate with limited memory or
      processing power, or with links that have high latency and/or low
      bandwidth. Existing Internet mail protocols are inefficient in
      such environments. The Lemonade working group is tasked to provide
      a set of email enhancements that permit efficient operation in
      resource-constrained computing and communication environments. The
      resulting specification(s) will be a seamless enhancement to
      existing Internet mail.

I have not said anything about MMS/WAP because I have no idea what
specifics are intended for dealing with them, in spite of your comments.
(Hence, for this issue, we are back to my original concern.)   More on
that, below.


Tuesday, February 25, 2003, 11:37:10 AM, you wrote:
TH> problem here is that there are a set of services which are being
TH> contemplated or deployed in specific environments which are based on
TH> IETF protocols but do not interoperate with them, either well or at all.

and i certainly agree that we should find a way to avoid that outcome.


TH> The list you saw above:  link characteristics, device characteristics,
TH> or service environments are the differences cited by those operating
TH> those service environments as reasons for wanting "profiles" of
TH> IETF protocols that meet their needs.

and I certainly agree that the current protocols work badly in a number
of environments.

Hence, unsolicited new mail notification and re-use of server-based
content will be spiffy enhancements.

I suspect the changes to support streaming content enhancement are
really something more general, and will "simply" do a graceful job of
moving the specifics of content handling to non-email subsystems,
tailored for the particular content. At any rate, yes of course that
will be a good enhancement too.


>>      "A primary goal of this work is to ensure that those profiles and
>>      enhancements continue to interoperate with the existing Internet
>>      email protocols in use on the Internet, so that these environments
>>      and more traditional Internet users have access to a seamless
>>      service."
>>
>>No doubt I am misinterpreting this, but it sure sounds as if the goal is
>>to create some sort of new email service and try to make sure it can be
>>gatewayed to existing Internet email services?

TH> Actually, avoiding the need to gateway between services is one of
TH> my own goals for this work.

I used the term "gateway" very carefully.  It is exactly what I get from
the current wording.

My world model of interconnection is very simple: either the upper-level
service is end-to-end and homogeneous, or the interface is between
independent, heterogeneous services. Multi-hop handling for the former
is relaying; for the latter is is gatewaying (ie, translating). Moving
the same content over different *underlying* environments is relaying.

From the current charter, I have no idea what is really intended,
concerning MMS/WAP, except that the style of the current language sure
makes me lean towards expecting gatewaying. (I'm delighted that you have
the intent of avoiding gatewaying, but now perhaps you can appreciate my
confusion.)

Perhaps the way to clarify this is to focus on what will be true of the
end participants, rather than what will not be true at the interface
between two parts of the service?  Hence, mentioning the interface
service because a derivative rather than a focus.

(Glad to thrash this privately with you, in an effort to come up with
alternate language. Again, I can't offer any yet, because I can't tell
what the specific issues and goals are.)

All of the above acknowledges that Time Is Passing(c).  Still, I've
become totally paranoid about charters that are vague.

d/
-- 
 Dave <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 t +1.408.246.8253; f +1.408.850.1850




From owner-ietf@ietf.org  Tue Feb 25 17:31:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20221;
	Tue, 25 Feb 2003 17:31:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18nnV1-0005NM-00
	for ietf-list@ran.ietf.org; Tue, 25 Feb 2003 17:24:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nnU3-0005Ja-00
	for ietf@ran.ietf.org; Tue, 25 Feb 2003 17:23:31 -0500
Received: from ithilien.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19907;
	Tue, 25 Feb 2003 17:13:29 -0500 (EST)
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h1PMHHYE019067;
	Tue, 25 Feb 2003 14:17:17 -0800 (PST)
Received: from CAMITLOAN6.qualcomm.com (camitloan6.qualcomm.com [129.46.225.112])
	by crowley.qualcomm.com (8.12.3/8.12.5/1.0) with ESMTP id h1PMHB5O014414;
	Tue, 25 Feb 2003 14:17:12 -0800 (PST)
Message-Id: <5.1.0.14.2.20030225134552.00b0f6d0@mage.qualcomm.com>
X-Sender: hardie@mage.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 25 Feb 2003 14:13:55 -0800
To: Dave Crocker <dcrocker@brandenburg.com>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to 
  support  diverse service environments (lemonade)
Cc: "Eric Burger" <eburger@snowshore.com>,
        "John C Klensin" <john-ietf@jck.com>, <ned.freed@mrochek.com>,
        "Pete Resnick" <presnick@qualcomm.com>, <ietf@ietf.org>,
        <iesg@ietf.org>, "IETF LEMONADE (E-mail)" <um@snowshore.com>
In-Reply-To: <10518983707.20030225125138@brandenburg.com>
References: <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com>
 <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
 <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com>
 <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:51 PM 2/25/2003 -0800, Dave Crocker wrote:
>I gather that the IAB is frankly dictating the current wording of the
>opening paragraph.

I don't know if something I said gave you that impression, but
it should not have.  I contributed text during a previous round
of discussions on the charter (before the last Lemonade BoF);
among them was the text you cited.  This was not an action
of the IAB; it was my personal suggestion.  If that was confusing
to anyone, I'm sorry that they did not seek clarification at the time.


>I am seriously dismayed to hear that.

If it were true, it would be a concern. I hope this puts that concern
to rest.


>  From an offline
>exchange, Ned mentions a desire to have the paragraph include something
>like "link characteristics of concern are those of high latency and low
>bandwidth, the device characteristics are limited memory and processing
>power, and the service environments are environments are MMS/WAP." I
>very heartily concur. In fact it is exactly what I think is missing.


I think chartering the working group to look at the problem, rather
than over-specifying the details is the right way to go here.  If
you think just about link characteristics for a moment, I think
you'll see that there are situations where non-congestive
loss might be more important than the available capacity of
the link.  This doesn't mean we should change the charter
to include the language; it means we should let the working
group figure it out.


>I used the term "gateway" very carefully.  It is exactly what I get from
>the current wording.
>
>My world model of interconnection is very simple: either the upper-level
>service is end-to-end and homogeneous, or the interface is between
>independent, heterogeneous services. Multi-hop handling for the former
>is relaying; for the latter is is gatewaying (ie, translating). Moving
>the same content over different *underlying* environments is relaying.

I agree that gatewaying implies transformation.  I think there
is a large rathole in trying to describe "Moving the same content
over different *underlying* environments" because there are
different ways of understanding what "same content" means.
I'd like to see us avoid that rathole entirely.


>(Glad to thrash this privately with you, in an effort to come up with
>alternate language. Again, I can't offer any yet, because I can't tell
>what the specific issues and goals are.)

Of the cc list of your message, I'd suggest "um@snowshore.com"
as the appropriate place to discuss the matter.

                                         regards,
                                                 Ted Hardie







From owner-ietf@ietf.org  Tue Feb 25 23:34:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28126;
	Tue, 25 Feb 2003 23:34:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ntDE-0006PS-00
	for ietf-list@ran.ietf.org; Tue, 25 Feb 2003 23:30:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ntCd-0006MB-00
	for ietf@ran.ietf.org; Tue, 25 Feb 2003 23:29:55 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27667
	for <ietf@ietf.org>; Tue, 25 Feb 2003 23:19:50 -0500 (EST)
Received: from bbprime.brandenburg.com (208.184.79.252.songbird.com [208.184.79.252] (may be forged))
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id UAA03814
	for <ietf@ietf.org>; Tue, 25 Feb 2003 20:23:28 -0800
Date: Tue, 25 Feb 2003 20:23:39 -0800
From: Dave Crocker <dhc2@dcrocker.net>
X-Mailer: The Bat! (v1.63 Beta/6) Personal
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <19546104865.20030225202339@brandenburg.com>
To: ietf@ietf.org
Subject: Re: Information on Directorates and Finances
In-Reply-To: <253493554.1044268894@localhost>
References: <253493554.1044268894@localhost>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,


From the financials:
HTA> The terminal room cost is $0 in 2001 because all 3 IETF meetings
HTA> were hosted. In 2003, we expect to have at least one, and possibly
HTA> two, non-host meetings, which means that terminal room costs will
HTA> come out of the secretariat's budget.

Perhaps it is again time to suggest forming a standing "terminal access"
committee, to help ensure timely, reliable, performant net access, etc.?

Although we seem to have been spared visible disasters in the last few
years, delivery of these services has periodically still been a very
close call, requiring emergency and herculean intervention of some
senior talent.

The technical and operations requirements for these events are actually
a bit unusual, especially since the physical aspects of the venue affect
wireless so much.  Therefore each new team has had a learning curve for
the process.

So why not recruit the talent ahead of time, use it for planning and
setup, working at a more deliberate pace, deliverying on experience with
our needs, and avoiding the crises and risk?


d/
--
 Dave Crocker <mailto:dcrocker@brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>




From owner-ietf@ietf.org  Wed Feb 26 11:25:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14651;
	Wed, 26 Feb 2003 11:25:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o4HI-0005WZ-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 11:19:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18o42a-0002ez-00
	for ietf@ran.ietf.org; Wed, 26 Feb 2003 11:04:16 -0500
Received: from zak.ecotroph.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13057;
	Wed, 26 Feb 2003 10:54:04 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
  (uid 2527)
  by zak.ecotroph.net with local; Wed, 26 Feb 2003 10:57:08 -0500
X-IMAP-Sender: leslie
Date: Wed, 26 Feb 2003 10:54:45 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>,
        "IETF LEMONADE (E-mail)" <um@snowshore.com>
CC: Ted Hardie <hardie@qualcomm.com>, Eric Burger <eburger@snowshore.com>,
        John C Klensin <john-ietf@jck.com>, ned.freed@mrochek.com,
        Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org, iesg@ietf.org
Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to support
 diverse service environments (lemonade)
References: <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com> <4A3384433CE2AB46A63468CB207E209D097BFB@zoe.office.snowshore.com> <5.1.0.14.2.20030225105642.00a777f8@mage.qualcomm.com> <10518983707.20030225125138@brandenburg.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <courier.3E5CE3D4.00005FA2@ecotroph.net>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Howdy,

Dave Crocker wrote:
> I gather that the IAB is frankly dictating the current wording of the
> opening paragraph. 

I don't know how you gathered this, but you'll be relieved
to know it isn't true.

There were concerns raised within the IAB and IESG with the
original phrasing of the charter, and the current text was
proposed as a revision back to the IAB and IESG as something
that addressed the concerns.  It did.  Presumably other formulations
would as well.  Your AD has the challenge of reconciling
concerns and revisions (in both directions).

Leslie.

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat 

Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------





From owner-ietf@ietf.org  Wed Feb 26 16:31:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26602;
	Wed, 26 Feb 2003 16:31:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9BQ-0002Uv-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:33:44 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lJiq-0003w3-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 21:12:32 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14854;
	Tue, 18 Feb 2003 21:04:11 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id UAA00864;
	Tue, 18 Feb 2003 20:57:36 -0500
Date: Tue, 18 Feb 2003 20:58:55 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <200302190054.h1J0sU4U003065@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302182015150.1529-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 19 Feb 2003 Mark.Andrews@isc.org wrote:

> > Good. You found a bug in an implementation. I thought such things were
> > off-topic for this list.  This bug doesn't mean that AXFR is broken.
> > Bind 8 did not have this bug, yet it has the common understanding of AXFR.
> >
> > Let me summarize the discussion:
> >
> > Everyone agrees that AXFR specification in RFC 1034 is ambiguous.
> >
> > Some people, many associated with Bind 9 development, assert that it is
> > necessary to change AXFR to support IXFR.  This assertion has been refuted
> > on the grounds that incremental database update does not depend on AXFR,
> > since incremental database update does not depend on the underlying wire
> > protocol used to create the remote database which is to be modified by
> > IXFR. Conceivably, it is unnecessary to use AXFR at all, yet one could
> > still use IXFR, so, AXFR is independent of IXFR.
>
> 	Nobody is saying that preserving zone content is a *wire*
> 	issue.  It is a server behaviour issue.

Zone definition and content is not an AXFR issue.  Server administrators
provide the definition of zone boundaries. (RFC 1034 Section 2.3 and
elsewhere)  AXFR merely gives the contents of the zone as has been defined
according to the boundaries and content specified by the administrator.
The contents could be given to the secondary by FTP or other method.  If
you mean to change the definition of zone contents, then I would say this
proposal is hugely mis-labeled.

All the IXFR server needs to do is determine (by some implementation
dependent, administrator maintained method) what has changed between one
zone version and another. How it does this is nobody's business but the
administrator and the implementor. There are infinite possibilities, here.
One could, for example, store differences in a series of files. The
administrator could even make the differnce files by hand--this is an
_implementation detail_. The IXFR server just sends a series or sequences
consisting of a list of deleted RRs and a list of added RRs to an IXFR
client. There is nothing more to it. (notwithstanding the optional
condensation.)

The IXFR client must simply make the changes (again, by some
implementation dependent, administrator maintained method) to the zone by
deleting RRs and adding RR's in each sequence. The original version of the
zone might have been obtained by FTP (or quantum interference, or the
psychic network) for all we know.

This isn't rocket science, and doesn't require any AXFR changes. Nor does
it require that the zone boundaries be defined only in some certain way,
beyond the definition of zone boundaries given by the system
administrator.

> > Some people, many associated with Bind 9 development, assert that AXFR as
> > commonly implemented by many implementors over many years, is broken, and
> > can't transfer domains correctly.  This claim has been refuted by
> > demonstration by interoperability between Bind 8 and other nameserver
> > implementations over the years, and 77% of the internet that currently
> > does not use Bind 9, yet still does AXFR.
>
> 	All this shows is that these nameservers are not used in
> 	situations where the breakage is demonstrated or the
> 	administators have learn to work around the breakage or
> 	choose to live with it or are unaware of it.

"administrators have learn[ed] to work around [it,...] live with it [,] or
are unaware of it".  Agreed.  Having done so, we don't want to stir the
pot.

Essentially, you are putting more (unnecessary) constraints on
implementations, and thus on the administrators, who are supposed to be
pretty free to define the zone boundaries.  Of course, the specifics of an
implementation puts some constraints on the adminstrator, but the
administrator can choose a different implementation more to her liking.

These unnecessary constraints are a "bad thing".

> > To prevent confusion between the two proposals, I would like to rename the
> > first proposal "Bind 9 AXFR Modification", and the second proposal "AXFR
> > Clarification". The term "axfr-clarify" will not be used.

I presume agreement on the name change?

		--Dean






From owner-ietf@ietf.org  Wed Feb 26 16:31:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26599;
	Wed, 26 Feb 2003 16:31:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9AN-0002OS-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:32:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18joyY-0002ee-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 18:10:34 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08622;
	Fri, 14 Feb 2003 18:03:14 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA19762;
	Fri, 14 Feb 2003 17:56:31 -0500
Date: Fri, 14 Feb 2003 17:57:45 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <200302142234.h1EMYOwZ011558@turing-police.cc.vt.edu>
Message-ID: <Pine.LNX.4.44.0302141750260.3790-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

As you note, they didn't conform to a BCP. There is no requirement (or
implication even) that one should conform to a Best Common Practice.
These serve to distribute helpful advice to the community and document
practices that have worked for others, in situations that may be
different.

The AXFR issue is compliance with a required standard, and its definition.
Much more serious concerns and issues are at stake.

		--Dean

On Fri, 14 Feb 2003 Valdis.Kletnieks@vt.edu wrote:

> On Fri, 14 Feb 2003 13:48:09 EST, Dean Anderson said:
>
> > It seems quite odd that a "clarification" would put 77% of the existing
> > servers out of compliance, and only brings into compliance a currently
> > non-compliant implementation.  I think it is unprecedented in the history
> > of any standards organization, not just the IETF.  Such a significant
> > change is clearly a completely new version.  Thus the widespread
> > complaints about fraudulent labeling and discription of the proposal.
>
> Granted, it's only a BCP, but see RFC2505.  A large percentage of
> implementations were non-conforming to THAT too - but the situation has
> improved dramatically since then.  And note that there are more servers
> for *THAT* protocol, from more vendors, than for DNS.
>
>
> --
> 				Valdis Kletnieks
> 				Computer Systems Senior Engineer
> 				Virginia Tech
>
>






From owner-ietf@ietf.org  Wed Feb 26 16:31:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26630;
	Wed, 26 Feb 2003 16:31:53 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9AO-0002OY-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:32:40 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lHX1-00081n-00
	for ietf@ran.ietf.org; Tue, 18 Feb 2003 18:52:11 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11698;
	Tue, 18 Feb 2003 18:43:52 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id SAA23308;
	Tue, 18 Feb 2003 18:45:00 -0500
Date: Tue, 18 Feb 2003 18:46:19 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Bind 9 AXFR Modification vs AXFR Clarification
In-Reply-To: <200302180227.h1I2RSd6053173@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302181821280.1529-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Good. You found a bug in an implementation. I thought such things were
off-topic for this list.  This bug doesn't mean that AXFR is broken.
Bind 8 did not have this bug, yet it has the common understanding of AXFR.

Let me summarize the discussion:

Everyone agrees that AXFR specification in RFC 1034 is ambiguous.

Some people, many associated with Bind 9 development, assert that it is
necessary to change AXFR to support IXFR.  This assertion has been refuted
on the grounds that incremental database update does not depend on AXFR,
since incremental database update does not depend on the underlying wire
protocol used to create the remote database which is to be modified by
IXFR. Conceivably, it is unnecessary to use AXFR at all, yet one could
still use IXFR, so, AXFR is independent of IXFR.

Some people, many associated with Bind 9 development, assert that AXFR as
commonly implemented by many implementors over many years, is broken, and
can't transfer domains correctly.  This claim has been refuted by
demonstration by interoperability between Bind 8 and other nameserver
implementations over the years, and 77% of the internet that currently
does not use Bind 9, yet still does AXFR.

There being no other arguments raised for the Bind 9 AXFR
clarify/modification proposal, it seems that this proposal is gratuitous
and unnecessary, and should be rejected.

However, we still have the issue of AXFR ambiguity to deal with, and we
still need to clarify those ambiguities.  I would therefore like to
organize a small group of people using implementations other than Bind 9,
which we declare to be broken, to document the common implementation
assumptions made, and submit that as a clarification to RFC 1034

To prevent confusion between the two proposals, I would like to rename the
first proposal "Bind 9 AXFR Modification", and the second proposal "AXFR
Clarification". The term "axfr-clarify" will not be used.

		--Dean







From owner-ietf@ietf.org  Wed Feb 26 16:31:55 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26672;
	Wed, 26 Feb 2003 16:31:55 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9FC-0002u9-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:37:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lbzE-00016m-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 16:42:40 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09440;
	Wed, 19 Feb 2003 16:34:07 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id QAA28236;
	Wed, 19 Feb 2003 16:30:46 -0500
Date: Wed, 19 Feb 2003 16:32:01 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <200302190342.h1J3gM4U003505@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302191621400.6276-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On Wed, 19 Feb 2003 Mark.Andrews@isc.org wrote:

> > All the IXFR server needs to do is determine (by some implementation
> > dependent, administrator maintained method) what has changed between one
> > zone version and another. How it does this is nobody's business but the
> > administrator and the implementor. There are infinite possibilities, here.
> > One could, for example, store differences in a series of files. The
> > administrator could even make the differnce files by hand--this is an
> > _implementation detail_. The IXFR server just sends a series or sequences
> > consisting of a list of deleted RRs and a list of added RRs to an IXFR
> > client. There is nothing more to it. (notwithstanding the optional
> > condensation.)
>
> 	All of which is irrelevent to this issue.

THAT's what I have been saying. You were the one who said we needed to do
this to support IXFR. I've been saying that claim was wrong. Thanks for
FINALLY coming round to that.

> > The IXFR client must simply make the changes (again, by some
> > implementation dependent, administrator maintained method) to the zone by
> > deleting RRs and adding RR's in each sequence. The original version of the
> > zone might have been obtained by FTP (or quantum interference, or the
> > psychic network) for all we know.
>
> 	Well the problem is that you have to get the *original* version,
> 	not a corrupted version.  AXFR implementations are not returning
> 	the data originally entered.

They sure have been.

> > This isn't rocket science, and doesn't require any AXFR changes. Nor does
> > it require that the zone boundaries be defined only in some certain way,
> > beyond the definition of zone boundaries given by the system
> > administrator.
>
> 	It does however require that for a given serial number that all
> 	sources of the zone have supplied identical contents.  You should
> 	be able to apply a IXFR delta to a copy derived from any source
> 	and have it apply without error.

None of this is relevant. All that is necessary is to delete the RRs, and
insert the RRs in the sequence.

If the zones are inconsistent through administrative mistake, then it
won't matter what the IXFR does.

> > > > Some people, many associated with Bind 9 development, assert that AXFR as
> > > > commonly implemented by many implementors over many years, is broken, and
> > > > can't transfer domains correctly.  This claim has been refuted by
> > > > demonstration by interoperability between Bind 8 and other nameserver
> > > > implementations over the years, and 77% of the internet that currently
> > > > does not use Bind 9, yet still does AXFR.
> > >
> > > 	All this shows is that these nameservers are not used in
> > > 	situations where the breakage is demonstrated or the
> > > 	administators have learn to work around the breakage or
> > > 	choose to live with it or are unaware of it.
> >
> > "administrators have learn[ed] to work around [it,...] live with it [,] or
> > are unaware of it".  Agreed.  Having done so, we don't want to stir the
> > pot.
>
> 	LOL.

Strange, that was my reaction, too. I'm just trying to be polite.  77%
work just fine. We don't want to break 77% of the servers out there.

> > Essentially, you are putting more (unnecessary) constraints on
> > implementations, and thus on the administrators, who are supposed to be
> > pretty free to define the zone boundaries.  Of course, the specifics of an
> > implementation puts some constraints on the adminstrator, but the
> > administrator can choose a different implementation more to her liking.
>
> 	The constaint was already there and it is necessary for reliable
> 	operation of the DNS.

No, you ware not being honest about the contents of the Draft. See my last
message to Andreas.

> > > > To prevent confusion between the two proposals, I would like to rename th
> > e
> > > > first proposal "Bind 9 AXFR Modification", and the second proposal "AXFR
> > > > Clarification". The term "axfr-clarify" will not be used.
> >
> > I presume agreement on the name change?
>
> 	No.

Then the entire draft should be rejected since it is misleading.  Please
resubmit a proposal that isn't misleading the community about its purpose,
impact, and contents.

		--Dean






From owner-ietf@ietf.org  Wed Feb 26 16:32:03 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26707;
	Wed, 26 Feb 2003 16:32:03 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9FC-0002uK-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:37:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ltmi-0005sd-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 11:42:56 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20329;
	Thu, 20 Feb 2003 11:34:10 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id LAA27216;
	Thu, 20 Feb 2003 11:31:27 -0500
Date: Thu, 20 Feb 2003 11:32:38 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <200302192356.h1JNuj4U006653@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302201039370.11133-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

> > > > The IXFR client must simply make the changes (again, by some
> > > > implementation dependent, administrator maintained method) to the zone by
> > > > deleting RRs and adding RR's in each sequence. The original version of th
> > e
> > > > zone might have been obtained by FTP (or quantum interference, or the
> > > > psychic network) for all we know.
> > >
> > > 	Well the problem is that you have to get the *original* version,
> > > 	not a corrupted version.  AXFR implementations are not returning
> > > 	the data originally entered.
> >
> > They sure have been.
>
> 	Not always.

You haven't shown any proof of that.  The "proof" you showed, was the
result of a misconfiguration.

> > If the zones are inconsistent through administrative mistake, then it
> > won't matter what the IXFR does.
>
> 	Who said anything administrative mistakes?  The content is being
> 	unilaterally changed by the servers.

It is reasonable and necessary to merge in glue. When you misconfigure the
glue, strange things may happen. That is all that you have shown.  I'm
sure that many software programs will exhibit even stranger behavior, and
may even fail to operate as a result of misconfiguration.

> > Strange, that was my reaction, too. I'm just trying to be polite.  77%
> > work just fine. We don't want to break 77% of the servers out there.
>
> 	You really think that it will break those servers?  LOL.

They will not be compliant, and thus will need to be changed. Thus, they
would be broken by definition of not being compliant.

Your failure to comprehend the consequences of the changes does not lessen
the effect.  We now agree that these changes aren't necessary to support
IXFR. You were part of the bad engineering that led to the unnecessary
creation of these changes in Bind 9.  You were also part of the bad
decision making that led to the distribution of these changes to Bind 9
users prior to standardization, and quite possibly you were part of the
bad decision making that resulted in publishing a book on the subject,
prior to acceptance of your modifications to standards. In short, you have
shown bad judgement.

Trying to "belittle" the effects with the "LOL", as opposed to offering
anything substantive, simply suggests that you have no appreciation of the
seriousness of the changes.  Perhaps you should take this more seriously.

> > > > Essentially, you are putting more (unnecessary) constraints on
> > > > implementations, and thus on the administrators, who are supposed to be
> > > > pretty free to define the zone boundaries.  Of course, the specifics of a
> > n
> > > > implementation puts some constraints on the adminstrator, but the
> > > > administrator can choose a different implementation more to her liking.
> > >
> > > 	The constaint was already there and it is necessary for reliable
> > > 	operation of the DNS.
> >
> > No, you ware not being honest about the contents of the Draft. See my last
> > message to Andreas.
>
> 	The abstract say:
>
> 				    This memo clarifies, updates, and
>    adds missing detail to the original AXFR protocol specification in
>    RFC1034.
>
> 	I fail to see how the contents can be deemed misleading when
> 	it states up front what it does.  Woops we missed warning you
> 	up front that it contains a warning.

I've no doubt that you fail to see it. We seem to be focusing a lot on
your failures. I have to question whether someone who went to MIT could
really fail so often. Perhaps it has changes since I was there. Or perhaps
you aren't really taking this very seriously. Let me explain it:

1) It doesn't say that it adds a completely new, incompatible zone
transfer protocol.  New protocols should be made through a different
process, which includes experimentation. I'm not against experimenting
with a new protocol. Indeed, I think this idea has some merit. However, it
can't be "end-run standardized" by a "clarification". There is a process.

2) It doesn't say that it changes AXFR with respect to SIG

3) It doesn't say that it changes the status of other RFC's (RFC 2845, and
possibly others.) without going through the appropriate standards process.

4) It doesn't say that it changes the definition of zone data to be
public. Zone data is absolutely not "public by definition". It could very
well be useful to tag certain RRs as non-public, and exclude them from
zone transfers to public servers. This "clarification" precludes that.
This is really 2 changes.

5) It doesn't say that it changes the security constraints on a zone
transfer to be limited to deny or accept only.

The list is longer, but that should be enough.









From owner-ietf@ietf.org  Wed Feb 26 17:00:59 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28258;
	Wed, 26 Feb 2003 17:00:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9FD-0002uX-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:37:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m2lI-0008B6-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 21:18:04 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06388;
	Thu, 20 Feb 2003 21:09:14 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id VAA05875;
	Thu, 20 Feb 2003 21:06:38 -0500
Date: Thu, 20 Feb 2003 21:07:49 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <200302202233.h1KMXO4U009264@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302201959400.13516-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:

> > You haven't shown any proof of that.  The "proof" you showed, was the
> > result of a misconfiguration.
>
> 	No.  It is the result of operational reality.  Whenever you
> 	have a parent and child zones under different administrative
> 	controls it is impossible to change both zones simultaniously.
> 	It is also impossible using AXFR or any other mechanism
> 	which transfers *individual* zones to transfer them to a
> 	secondary and guarantee that they will arrive simultaniously.
>
> 	Having parent and child zone under different administrative control
> 	is the norm not the execption.

Actually, a parent always has some control over the child. It exercises
this control through the glue records.  When the glue records are in the
child zone, they need to be merged. If a zone transfer happens while they
are inconsistent, it is possible for some strange results to happen.
Ordinarilly, zone transfers don't happen when they are inconsistent, since
the inconsistency is usually short.

Any zone transfers made during the inconsistent window are corrected so
long as the child zone is updated with correct information after the
parent is updated.

Frequently the parent and child zone are under different administrative
control, and are frequently on different servers. In such a case, the
contents of the parent zone aren't merged with the child in the child's
server, and no evidence of the inconsistency is seen through zone
transfers. However, the inconsistency still exists and may still be
visible by resolvers and nameservers that lookup the glue records.

You have obtained no benefits by these constraints.

> > > > If the zones are inconsistent through administrative mistake, then it
> > > > won't matter what the IXFR does.
> > >
> > > 	Who said anything administrative mistakes?  The content is being
> > > 	unilaterally changed by the servers.
> >
> > It is reasonable and necessary to merge in glue. When you misconfigure the
> > glue, strange things may happen. That is all that you have shown.  I'm
> > sure that many software programs will exhibit even stranger behavior, and
> > may even fail to operate as a result of misconfiguration.
>
> 	No.  It is neither reasonable nor necessary.  Any temporary
> 	inconsistancies will be corrected when all the zone transfers
> 	complete.  By changing the zones contents you create
> 	situations where these temporary inconsistancies won't be
> 	corrected.  When handing out non axfr/ixfr responses you
> 	use the best source of data you have.

It is necessary, since the parent has glue records in the child zone.
The parent therefore has (always) a part of the child zone. If that server
also loads the child zone (or perhaps generates part of it dynamically),
it quite reasonable to merge the records as though the zone includes
multiple files, which in theory, it does.

The child zone contents will only be correct when the administrators of
both zones agree on the contents of the glue records, and update their
parts of the child zone accordingly. It will not be correct until then,
regardless of how many zone transfers take place.

> 	Nothing in RFC 1033 / 1034 / 1035 says that a server is permitted
> 	to alter the content of a zone.  The responability for maintaining
> 	consistancy between zones is a administrative function.

This is a loaded statement. The part of the server NOT involved in
responding to queries and zone transfers is part of the administrative
function. So, as part of that administrative function, it has to be able
to modify the RR and zones accordingly.  Your proposed changes exclude a
huge part of the potential for intelligence in name servers. And do so
with no benefits.

> > > > Strange, that was my reaction, too. I'm just trying to be polite.  77%
> > > > work just fine. We don't want to break 77% of the servers out there.
> > >
> > > 	You really think that it will break those servers?  LOL.
> >
> > They will not be compliant, and thus will need to be changed. Thus, they
> > would be broken by definition of not being compliant.
>
> 	So.  Just because they will not be compliant doesn't mean
> 	that that they need to be replaced immediately.  That
> 	non-compliance doesn't hurt most of them.  For those where
> 	it does have a negative impact it will mean that they should
> 	be able to request a fix from their vendor.

You seem to make a case that in general, non-compliance doesn't hurt
anything. This is false, for both technical and commercial reasons.
Technically, it hurts interoperability, which has some many obvious harms
I won't go into them. Commercially, implementations make and advertise
compatibility and standards compliance claims. This retroactively makes
those claims false, which harms the business and reputation of those other
vendors.

77% will need a fix from the vendor, if we were to accept these changes.

The vendor that made false claims of compatibility and standards
compliance is Bind 9. It should suffer the commercial damage to its
business and reputation, as a result.

> > Your failure to comprehend the consequences of the changes does not lessen
> > the effect.  We now agree that these changes aren't necessary to support
> > IXFR. You were part of the bad engineering that led to the unnecessary
> > creation of these changes in Bind 9.  You were also part of the bad
> > decision making that led to the distribution of these changes to Bind 9
> > users prior to standardization, and quite possibly you were part of the
> > bad decision making that resulted in publishing a book on the subject,
> > prior to acceptance of your modifications to standards. In short, you have
> > shown bad judgement.
>
> 	I never said that they we not necessary for IXFR.  I said that
> 	that your descripition of how to generate the differences was
> 	irrelevent to this discussion.

Ok, you are half way there. They are irrelevant because IXFR is
irrelevant. These changes are not necessary to IXFR, as I explained that
IXFR can work with the current AXFR, or even without AXFR.

> 	It was bad engineering to merge the data sets together in the
> 	first place.  It was not required by RFC 1033/ 1034 / 1035.
> 	It had negative consequences.  It was good engineering to
> 	correct this.  It was also good engineering to report a
> 	common error to the community so that other vendors could
> 	fix their mistakes.

Actually, since the parent has the glue in the child zone, it has part of
the child zone as well as the master zone.  Merging them together is not
prohibited, and in the case where child and parent have the same
adminstrator, as might be the case where most of the child is simply
automatically generated by the nameserver, can make things much easier.

Your constraints preclude this unnecessarilly.

Since I can think of cases where it is useful to merge records together,
it is bad engineering to remove that flexibility and obtain no benefits in
return.

> > Trying to "belittle" the effects with the "LOL", as opposed to offering
> > anything substantive, simply suggests that you have no appreciation of the
> > seriousness of the changes.  Perhaps you should take this more seriously.
>
> 	I'm quite aware of what the change requires.  I'm also aware
> 	that most of the nameserver are used in situations where
> 	the zone contents is already preserved because they are not
> 	serving zones with parent / child relationships.

Apparently, you aren't even aware that your changes will make all non-bind
9 servers non-compliant.  Had you been aware of that, it seems you would
have brought this proposal forward something like 3 years ago, before
releasing Bind 9, and before publishing a book on the subject.

> 	Anyone saying that all the nameservers need to be replaced
> 	immediately is spreading FUD.  LOL the the correct reponse
> 	to FUD.

Making 77% of the servers non-compliant is a fact of your proposed
changes.  It is another fact, as explained, that non-compliant servers
will need to be replaced.  Will they suddenly stop working? It depends on
whether other implementations want to implement a "backwards
compatibility" mode. If they don't implement this mode, then the answer is
yes, they will stop working as soon as these updates are deployed by other
vendors. Of course, this is a bad result.

> 	Using a server that perserves zone contents under all
> 	conditions doesn't break anything.

Your constraints break useful services, and offer no value in return.

> > 1) It doesn't say that it adds a completely new, incompatible zone
> > transfer protocol.  New protocols should be made through a different
> > process, which includes experimentation. I'm not against experimenting
> > with a new protocol. Indeed, I think this idea has some merit. However, it
> > can't be "end-run standardized" by a "clarification". There is a process.
>
> 	It isn't new.  All it is saying is that the contents tramitted
> 	out MUST be that transmitted in.  This occurs most of the time
> 	already.  Note BIND is not the only implementation that does
> 	this.  We have already had reports of 3 other implementations
> 	doing this.  Even the implementations that don't guarentee the
> 	contents do this most of the time.  It has no negative effects.

No, Section 3.1 is a whole new derivative of AXFR. That is new.

> > 2) It doesn't say that it changes AXFR with respect to SIG
>
> 	It doesn't change anything wrt to SIG.  Go read RFC 2535 which
> 	also says that SIG records in the answer section are part of the
> 	zone contents and don't need special processing.

Oh. Then section 3.3 can be deleted in entirety without objection.

> > 3) It doesn't say that it changes the status of other RFC's (RFC 2845, and
> > possibly others.) without going through the appropriate standards process.
>
> 	It doen't change the status of RFC 2845.

The IEFT index indicates that RFC 2845 is "Proposed Standard", with no
applicability statement that I could find.  This changes it to
"RECOMMENDED" requirement level.  I think an applicability statement is
premature until RFC 2845 is moved along, and then by the appropriate
standards body decision-making process. It is inappropriate to hide
something like this deep in an irrelevant "clarification".

> > 4) It doesn't say that it changes the definition of zone data to be
> > public. Zone data is absolutely not "public by definition". It could very
> > well be useful to tag certain RRs as non-public, and exclude them from
> > zone transfers to public servers. This "clarification" precludes that.
> > This is really 2 changes.
>
> 	Nowhere in RFC 1033 / 1034 / 1035 does it say that zone transfers
> 	are restricted to secondaries.  Nowhere in RFC 1033 / 1034 / 1035
> 	does it say that you should restrict zone tranfers.

I don't think you understood my statement. I'm talking about the
definition of zone data. Nowhere does 1034 etc say that zone data is
public.  It may well have been thought to be public, originally, but since
I can easily see a useful purpose in withholding some private RRs, there
isn't any reason to preclude that behavior.

Your constraints harm a useful purpose, and provide no benefits.

> 	There is a REFUSED rcode so the possibility of refusing a zone
> 	transfer is allowed for but the conditions underwhich this will
> 	be done are not specified.  This draft does not change this.

Your modifications put additional and unnecessary restrictions on a zone
transfer. Again, these restrictions have no useful purpose.

> > 5) It doesn't say that it changes the security constraints on a zone
> > transfer to be limited to deny or accept only.
>
> 	Effective it does.  If you transmit the zone then you MUST
> 	transmit its full contents unmodified (accept).  It also
> 	says that you are allowed to refuse zone transfers (deny).

This was addressed in the previous comments.







From owner-ietf@ietf.org  Wed Feb 26 17:08:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28540;
	Wed, 26 Feb 2003 17:08:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9GA-00030n-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:38:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mIgQ-00067p-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 14:18:06 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11535;
	Fri, 21 Feb 2003 14:09:01 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA29747;
	Fri, 21 Feb 2003 14:05:28 -0500
Date: Fri, 21 Feb 2003 14:06:41 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: ietf@ietf.org, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification
In-Reply-To: <20030221063725.35914.qmail@cr.yp.to>
Message-ID: <Pine.LNX.4.44.0302211404410.17772-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk



On 21 Feb 2003, D. J. Bernstein wrote:

> Mark.Andrews@isc.org writes:
> > Whenever you have a parent and child zones under different administrative
> > controls it is impossible to change both zones simultaniously.
>
> False.
>
> Set the clocks correctly, and schedule the change on all the servers for
> a particular time, using (for example) the tinydns timestamp feature
> described in http://cr.yp.to/djbdns/tinydns-data.html. When that time
> rolls around, all the servers will change their data simultaneously, as
> RFC 1034 requires.

Clever.

> Yes, this is difficult to achieve with BIND, AXFR, etc. But it's easy to
> achieve with better software, better replication protocols, etc. You're
> making a fool of yourself when you call it ``impossible.''

This could be done with a slight change to AXFR. Lets include it in the
MAXFR proposal (the axfr mods, taken out of the "clarification".







From owner-ietf@ietf.org  Wed Feb 26 17:11:12 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28705;
	Wed, 26 Feb 2003 17:11:12 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9GA-00030t-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:38:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18mIqK-0006ia-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 14:28:20 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11848;
	Fri, 21 Feb 2003 14:19:19 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id OAA17122;
	Fri, 21 Feb 2003 14:19:35 -0500
Date: Fri, 21 Feb 2003 14:20:57 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Erik Nordmark <Erik.Nordmark@sun.com>
cc: Mark.Andrews@isc.org, <mw-list-namedroppers@csi.hu>,
        Name Droppers <namedroppers@ops.ietf.org>, <ietf@ietf.org>,
        <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <Roam.SIMC.2.0.6.1045815936.14452.nordmark@bebop.france>
Message-ID: <Pine.LNX.4.44.0302211413080.17772-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

Interesting. So, they knew that standardization was necessary, the
proposed a standard, the standard wasn't accepted, so they distributed
code to users anyway, and wrote a book anyway.

I find that even more worthy of criticism.

Did they think they would force this through later? Never mind, it doesn't
matter what they thought.

As this "clarify" seems to have been dead for years, we should get on with
the business of clarifying AXFR as it was commonly interpreted. And lets
get on with the MAXFR proposal.

		--Dean

On Fri, 21 Feb 2003, Erik Nordmark wrote:

> > Apparently, you aren't even aware that your changes will make all non-bind
> > 9 servers non-compliant.  Had you been aware of that, it seems you would
> > have brought this proposal forward something like 3 years ago, before
> > releasing Bind 9, and before publishing a book on the subject.
>
> A data point.
>
> http://www.ietf.org/proceedings/00jul/I-D/dnsext-axfr-clarify-00.txt
> INTERNET-DRAFT                                      Andreas Gustafsson
> draft-ietf-dnsext-axfr-clarify-00.txt                     Nominum Inc.
>                                                             March 2000
> Seems to be 3 years ago.
>
>   Erik
>
>






From owner-ietf@ietf.org  Wed Feb 26 17:11:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28756;
	Wed, 26 Feb 2003 17:11:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9GB-00030z-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:38:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18jyUq-0002tg-00
	for ietf@ran.ietf.org; Sat, 15 Feb 2003 04:20:32 -0500
Received: from master.linux-ide.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29123
	for <ietf@ietf.org>; Sat, 15 Feb 2003 04:13:06 -0500 (EST)
Received: from localhost (andre@localhost)
	by master.linux-ide.org (8.9.3/8.9.3) with ESMTP id BAA12084;
	Sat, 15 Feb 2003 01:00:53 -0800
Date: Sat, 15 Feb 2003 01:00:53 -0800 (PST)
From: Andre Hedrick <andre@linux-ide.org>
To: Loa Andersson <loa@pi.se>
cc: RJ Atkinson <rja@extremenetworks.com>, "Mallikarjun C." <cbm@rose.hp.com>,
        Bob Braden <braden@ISI.EDU>, sob@harvard.edu, mankin@psg.com,
        ips@ece.cmu.edu, ietf@ietf.org
Subject: Re: Protocol Action: iSCSI to Proposed Standard
In-Reply-To: <3E4C9E1E.1010406@pi.se>
Message-ID: <Pine.LNX.4.10.10302150056570.10442-100000@master.linux-ide.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk



This would not logically include ignoring the rule about everything put to
the wire must be "BIG ENDIAN"?  Obviously everyone knows to ignore this
ruleset when dealing with CRC32C; however, if you are a "BIG ENDIAN" box
you must conform to make your CRC32C put on the wire in "LITTLE ENDIAN".

Of course this is me being picky about following the rules.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

On Fri, 14 Feb 2003, Loa Andersson wrote:

> 
> Ran,
> 
> would agree to this, and put even stronger
> 
> "... Internet RFCs the normal Inernet terminology SHOULD be used, unless 
> there
> are very stong and explicitly stated reasons not to ..."
> 
> it should als  be that the I* have a guiding role in this
> 
> /Loa
> 
> 
> RJ Atkinson wrote:
> 
> >
> > On Wednesday, Feb 12, 2003, at 13:24 America/Montreal, Mallikarjun C. 
> > wrote:
> >
> >>> All the Internet documentation with which I am familiar, as well as the
> >>
> >>
> >> I think we have a case of overlapping vocabulary from two different 
> >> domains.
> >>
> >> Per SCSI Architecture Model (SAM-2, SAM-3), iSCSI is very clearly
> >> a "SCSI transport protocol" (as opposed to a SCSI application layer 
> >> protocol).
> >> Parallel SCSI, Fibre Channel etc. are all "SCSI transports" per SCSI 
> >> conventions.
> >> That is all the critiqued abstract is trying to describe.
> >
> >
> > In the context of an *Internet* RFC, it seems sensible to use the normal
> > Internet terminology -- unless one very very clearly indicates that a
> > term is being used in some different semantic.  One might postulate that
> > the document's editors and RFC-Editor could work out a mutually agreeable
> > editorial change here to add clarity.
> >
> > Ran
> >
> >
> >
> >
> 






From owner-ietf@ietf.org  Wed Feb 26 17:17:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29038;
	Wed, 26 Feb 2003 17:16:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9u7-0003XN-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 17:19:55 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lRCZ-0001DV-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 05:11:43 -0500
Received: from ratree.psu.ac.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17577;
	Wed, 19 Feb 2003 05:03:12 -0500 (EST)
Received: from delta.cs.mu.OZ.AU ([172.30.0.189])
	by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h1JA6od11768;
	Wed, 19 Feb 2003 17:06:50 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h1JA3dK05450;
	Wed, 19 Feb 2003 17:03:41 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: "IETF consensus" in IANA considerations [was Re: Last Call: CR-LDP Extensions for ASON to Informational ] 
In-Reply-To: <31100000.1045575051@askvoll.hjemme.alvestrand.no> 
References: <31100000.1045575051@askvoll.hjemme.alvestrand.no>  <200301302045.h0UKjDF05128@cichlid.adsl.duke.edu> <20899.1044967504@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 19 Feb 2003 17:03:39 +0700
Message-ID: <5448.1045649019@munnari.OZ.AU>
Sender: owner-ietf@ietf.org
Precedence: bulk

    Date:        Tue, 18 Feb 2003 14:30:51 +0100
    From:        Harald Tveit Alvestrand <harald@alvestrand.no>
    Message-ID:  <31100000.1045575051@askvoll.hjemme.alvestrand.no>

  | Given that a large portion of the IETF does not in fact subscribe to the 
  | ietf-announce list,

That's irrelevant, anyone who cares can subscribe (or can request someone
else to forward any relevant messages).

Anyone who fails to subscribe to the list where last calls are made, is
effectively saying that they have no objection to anything the rest of the
IETF decides on some issue (just as not replying to a last call request
does - which is what most of us do to most last calls that are made).

  | and that in some cases the IETF consensus is pretty obvious

This gets dangerous.   What is obvious to one person, or one group of
people, is not always obvious to others.   It is certainly OK to send
one last call which asks several questions (may be harder to decide what
the consensus actually is if there's any contention, but that's an
operational issue).   In some cases it may even be possible to infer what
the consensus mush have been without explicitly mentioning an issue
(eg: last calls rarely mention that an RFC number will be issued by the
RFC editor - but I think it is pretty safe to assume that everyone knows
that if a document is published it will need an RFC number allocated to
it...   Similarly, documents that call for IANA assignments will, if
agreed to, require the IANA to actually make the necessary assignments).

But caution is needed here.   Jumping from "There is clear consensus for
X" to "There must be consensus for Y then" because "to do X we must do Y"
can be very dangerous, because the "to do X we must do Y" is very often
just an opinion - sometimes a very strongly held opinion, and in some
cases people think of it as "so obvious to not need discussion", but that
doesn't mean that there won't be other options - but they'll only appear
if requested.  So except in cases where it can really be shown that the
requirement for Y is fundamental for X (X cannot conceivably be done in
any other way, and no-one could reasonably suggest an alternative), err
on the side of caution, and send a last call to obtain opinions.

  | (for instance when the decision is just paperwork following up on 
  | another IETF consensus decision), I wouldn't even say that a Last Call is 
  | always required.

I would.   That's the definition (IMO) of IETF consensus.  However, I'm not
saying that there needs to be a separate last call for every individual
decision that is to be made (of those which require IETF consensus).

  | But it's certainly one tool, and a fairly powerful one, for getting 
  | objections out in public.

Do we have any other?

  | (now, does the recent DJB discussion of axfr-clarify by itself invalidate 
  | WG or IETF consensus? I think not.... but it's certainly input that has to 
  | be considered when determining the IETF consensus.)

I'm not sure on the relevance of this.   This looks to be more pertinent to
what it takes to determine whether IETF consensus actually exists.   No-one
would have considered making any decision on axfr-clarify without a last call
(or at least, not a decision to publish it on the standards track).

Once the last call has been issued, and people have had a chance to reply,
then someone (the IESG currently) has to determine whether there actually
is some kind of "rough consensus" or not from reading all of the responses.
I'm not claiming that's easy... but I don't think it is at all relevant
to the issue of whether or not a last call should be issued before the
decision on whether IETF consensus exists or not is taken.

kre






From owner-ietf@ietf.org  Wed Feb 26 17:17:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29040;
	Wed, 26 Feb 2003 17:17:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9uC-0003ZX-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 17:20:00 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18laEH-0005il-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 14:50:05 -0500
Received: from lion.ninthwonder.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06442
	for <ietf@ietf.org>; Wed, 19 Feb 2003 14:41:34 -0500 (EST)
From: wrstuden@wasabisystems.com
Received: by lion.ninthwonder.com (Postfix, from userid 1021)
	id 157CE30706; Wed, 19 Feb 2003 14:45:24 -0500 (EST)
Date: Wed, 19 Feb 2003 12:38:11 +0000 (UTC)
X-X-Sender: wrstuden@
To: Andre Hedrick <andre@linux-ide.org>
Cc: ips@ece.cmu.edu, ietf@ietf.org
Subject: Re: Protocol Action: iSCSI to Proposed Standard
In-Reply-To: <Pine.LNX.4.10.10302150056570.10442-100000@master.linux-ide.org>
Message-ID: <Pine.NEB.4.53.0302191234100.581@>
References: <Pine.LNX.4.10.10302150056570.10442-100000@master.linux-ide.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Sat, 15 Feb 2003, Andre Hedrick wrote:

> This would not logically include ignoring the rule about everything put to
> the wire must be "BIG ENDIAN"?  Obviously everyone knows to ignore this
> ruleset when dealing with CRC32C; however, if you are a "BIG ENDIAN" box
> you must conform to make your CRC32C put on the wire in "LITTLE ENDIAN".
>
> Of course this is me being picky about following the rules.

Funny you would mention that. The CRC32C actually DOES go out in a
Big-Endian manner, in terms of the CRC polinomial powers. It is just that
the polinomial powers have bit 7 (2^0) as being more significant than bit
0 (2^7).

Take care,

Bill





From owner-ietf@ietf.org  Wed Feb 26 17:17:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29111;
	Wed, 26 Feb 2003 17:17:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9uF-0003ae-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 17:20:03 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lsOs-0001XT-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 10:14:14 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16730
	for <ietf@ietf.org>; Thu, 20 Feb 2003 10:05:32 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 20 Feb 2003 07:09:22 -0800
X-Originating-IP: [203.124.140.38]
From: "john smith" <johnsmith0302@hotmail.com>
To: <ietf@ietf.org>
Subject: cables
Date: Thu, 20 Feb 2003 20:41:45 +0530
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <OE15OgRGkQ6mBySsxVY00008a4c@hotmail.com>
X-OriginalArrivalTime: 20 Feb 2003 15:09:22.0166 (UTC) FILETIME=[0C689160:01C2D8F2]
Sender: owner-ietf@ietf.org
Precedence: bulk


on ethernet,


If all ports were DTE pin configured (same pair everywhere for rx and tx)

and all cables were cross

life would be simpler.

-JS






From owner-ietf@ietf.org  Wed Feb 26 17:18:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29248;
	Wed, 26 Feb 2003 17:18:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9uG-0003b4-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 17:20:04 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lsiK-0002Vi-00
	for ietf@ran.ietf.org; Thu, 20 Feb 2003 10:34:20 -0500
Received: from prue.eim.surrey.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17667
	for <ietf@ietf.org>; Thu, 20 Feb 2003 10:25:37 -0500 (EST)
Received: from artemis.ee.surrey.ac.uk ([131.227.88.18] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4)
	id 18lsdN-0006ti-00; Thu, 20 Feb 2003 15:29:13 +0000
Date: Thu, 20 Feb 2003 15:29:12 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@artemis.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: grenville armitage <garmitage@swin.edu.au>
cc: ietf@ietf.org
Subject: Re: Warning about the use of abusive language
In-Reply-To: <3E54DFCF.61CEA099@swin.edu.au>
Message-ID: <Pine.GSO.4.50.0302201517580.10997-100000@artemis.ee.surrey.ac.uk>
References: <20030219190124.8908.qmail@cr.yp.to>  <200302192321.h1JNL94U006491@drugs.dv.isc.org>
  <20030220000752.38144.qmail@cr.yp.to> <809960000.1045731394@askvoll.hjemme.alvestrand.no>
 <3E54DFCF.61CEA099@swin.edu.au>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-103.0 required=5.5
	tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      USER_AGENT_PINE,USER_IN_WHITELIST
	version=2.44
X-Scanner: exiscan *18lsdN-0006ti-00*P2VMXgJIXLg* (SECM, UniS)
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 21 Feb 2003, grenville armitage wrote:

> Harald Tveit Alvestrand wrote:
> 	[..]
> > Accusations of "dishonesty" and "fraud" in a technical discussion are
> > normally considered "unprofessional".

...when they're unsubstantiated and unproven, certainly. Is that the
case?

> I'm finding Bernstein's commentary to be robust and colorful (and at times
> obtuse, for I'm not a DNS weenie and the relevant details usually elude me).
> But not even beginning to get as close to 'unprofessional' as I've seen
> on IETF mailing lists over the years.
>
> "Be liberal in what you accept" seems a good philosophy for reading this
> list...

Cuts both ways.

Anyone attempting to mail bernstein will have discovered that he's not
very liberal in what he accepts.

Anyone attempting to read bernstein will have discovered that he's not
very conservative in what he sends.

I have to keep reminding myself than bernstein is NOT a teenager, and
that I really shouldn't be making allowances for his age.

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@ee.surrey.ac.uk>





From owner-ietf@ietf.org  Wed Feb 26 17:25:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26601;
	Wed, 26 Feb 2003 16:31:51 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9AN-0002OM-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:32:39 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18joMu-0001Lp-00
	for ietf@ran.ietf.org; Fri, 14 Feb 2003 17:31:40 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07512;
	Fri, 14 Feb 2003 17:24:19 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id RAA29890;
	Fri, 14 Feb 2003 17:24:26 -0500
Date: Fri, 14 Feb 2003 17:25:40 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Andreas Gustafsson <gson@nominum.com>
cc: Robert Elz <kre@munnari.OZ.AU>, "D. J. Bernstein" <djb@cr.yp.to>,
        <ietf@ietf.org>, <iesg@ietf.org>, <namedroppers@ops.ietf.org>
Subject: Re: axfr-clarify's fraudulent claims of consensus 
In-Reply-To: <200302142024.h1EKOkS10983@guava.araneus.fi>
Message-ID: <Pine.LNX.4.44.0302141553360.3790-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Fri, 14 Feb 2003, Andreas Gustafsson wrote:
> Dean Anderson writes:
> > I don't think they can be dismissed so easilly. Indeed, I think the
> > proposed changes are rather "oddball", and are actually unncessary in
> > order to implement IXFR (which was the original claimed justification).
>
> This is not a "change".  There are no existing standards which mandate
> or even explicitly allow mixing of data between zones.  On the
> contrary, RFC1035 specifically suggests using separate data structures
> that ensure that no such mixing occurs:

The key word is "suggests", which has the meaning...

> Which one is more "oddball", a server which follows this suggestion or
> one which does not?

Neither. It doesn't matter what the implementation is. What matters is the
protocol. Despite the "suggestion", all implementations prior to Bind 9
made different (but ultimately identical) assumptions. I don't think the
section you quote is so compelling.

The "oddball" part is requiring a change to a irrelevant part of a
protocol.  This is nothing less than bad or lazy engineering.** As I
mentioned previously, IXFR is in principle no different from an Oracle
incremental replication. Clearly, one does not need to alter SQL to have
replicated databases.  One _could_ alter SQL, but it would be a "bad
idea".  The concepts of replicated databases, and different kinds of
replication is well researched, and well documented.  There isn't any
rocket science to IXFR, nor are there any theoretical papers to be written
on the subject. The AXFR protocol does not _need_ to be changed for IXFR.
IXFR can be made to work with AXFR the way it stands.

** a collection of good engineering principles:

A "good" engineer avoids making gratiutous changes.

A "good" engineer, thinking a significant change to a standard of
interoperability needs to be made, will seek consensus from the standards
body on the change before distributing it.

A "good" engineer, upon finding a language ambiguity or vagueness, would
investigate how others analyzed the language, what assumptions they made
about the ambiguity and follow accordingly, or discuss and resolve the
ambiguity if there are no concrete implementations.

A "good" engineer, realizing an incompatible change has to be made to a
standard of interoperabilty, would consult the standards body prior to
publishing a (non-interoperable) book on the subject.

A "good" manager, would ensure that engineers are making "good"
engineering decisions.

Pretty clearly, the Bind 9 group didn't exercise "good" engineering
principles, nor "good" engineering management.  Quite obviously, they made
a mistake altering and distributing AXFR prior to standardization, or by
exploiting the vagueness in the specification. Clearly, they knew about
the incompatibility issue.  One must wonder if anyone could be so arrogant
as to assume that they could push anything they pleased through the
standardization process.  We probably can't know the answer. I don't know
anything about their intentions and can only fairly judge the results of
their actions. However, there is much to criticize about the actions.  I
do not think I am being unfair in that criticism. I also realize that Bind
9 was a group effort, and there is blame to spread among many.

However, I do not want to pay for that mistake. Nor do others.

> > Indeed, the proposed changes are only necessary to justify BINDs' oddball
> > IXFR changes. They are only necessary to make BIND 9 compliant with the
> > RFC's.
>
> BIND 9 is compliant with the existing AXFR standard even without
> axfr-clarify.  It's not hard to comply since the existing the
> specification is almost nonexistent.

No. This isn't true either.  If we clarify AXFR to standardize the
_assumptions_ identically and concretely made by many implementors over a
long period of time, then BIND 9 will not be compliant**.  Bind 9 is
"compliant" only with the vague AXFR spec by invirtue of its vagueness.
AXFR should be clarified. I (and others) think it should be clarified to
follow the concrete assumptions made by many implementors over many years.
This will only make BIND 9 non-compliant.

Then 23% of the servers will have to change. 77% will be unaffected.
**Actually, it might not even be this bad, as I think there are some
"backwards compatibility" functionality that current Bind 9 users can
utilize. So perhaps no servers need changing if we standardize AXFR as I
propose. Except that Bind 9 will have to withdraw IXFR support until it
fixes it to work with AXFR as clarified, or make it synonomous with AXFR.

> > It seems quite odd that a "clarification" would put 77% of the existing
> > servers out of compliance,
>
> 77% of the existing servers do not reliably interoperate in IXFR (even
> with one another), and sometimes serve data inconsistent between the
> authoritative servers of a zone.  They *should* be declared out of
> compliance.

No, because IXFR support is essentially optional. An IXFR server can
return the whole zone (AXFR) if it doesn't support IXFR.  A server can be
compliant with RFC 1995 just by making IXFR a synonym for AXFR. That's
probably a one line change for most if not all implementations. Further,
most people are not using IXFR.

AXFR is not optional. Most people are using AXFR.

> > and only brings into compliance a currently
> > non-compliant implementation.
>
> Again, BIND 9 is currently compliant.

Bind 9 won't be compliant (modulo its "backward compatibilty") after
clarification of AXFR to specify the commonly assumed and commonly
implemented behavior for AXFR.

> > Consensus on the part of Bind proponents, yes. Consensus when the wider
> > community is counted, no.

> I have been reluctant to bring up this issue because because it should
> make no difference whatsoever - the draft should be judged solely on
> its technical merits, not based on the affiliations of its proponents,
> but the groundless accusations of misconduct and conspiracy theories
> by you and Dr. Bernstein have gone too far.

I have made no allegations. My position on the issue of "conspiracy and
misconduct" is that allegations made against Dr. Bernstein need to be
investigated, and the allegations made by Dr.  Bernstein also need to
investigated.  I think the allegations made by both sides are sufficiently
specific that a determination can be made as to their truth.

There are many on the djbdiscuss list who seem to think the issue deserves
investigation. (I will try to get back to that matter next week, and work
with others to come to a conclusion about which accusations were credible
and which accusations weren't.)  Clearly, some of the allegations made go
way too far.

		--Dean






From owner-ietf@ietf.org  Wed Feb 26 18:10:51 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29035;
	Wed, 26 Feb 2003 17:16:59 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9u9-0003Xe-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 17:19:57 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18lZ0d-0002pM-00
	for ietf@ran.ietf.org; Wed, 19 Feb 2003 13:31:55 -0500
Received: from carwash.centivinc.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03973;
	Wed, 19 Feb 2003 13:23:24 -0500 (EST)
Received: from minglewood.incentivesystems.com ([172.16.0.25])
 by carwash.centivinc.com (NAVGW 2.5.2.11) with SMTP id M2003021913295723565
 ; Wed, 19 Feb 2003 13:29:57 -0500
Received: from centive.com ([10.10.51.177]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 19 Feb 2003 13:24:56 -0500
Message-ID: <3E53CBF9.4040002@centive.com>
Date: Wed, 19 Feb 2003 13:24:57 -0500
From: John Stracke <jstracke@centive.com>
Organization: Centive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tomson_Eric@Yahoo.fr
CC: "'Harald Tveit Alvestrand'" <harald@alvestrand.no>, ietf@ietf.org,
        iesg@ietf.org, namedroppers@ops.ietf.org
Subject: Re: Just three questions
References: <002d01c2d841$726dd670$1100a8c0@tomson.be>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Feb 2003 18:24:56.0996 (UTC) FILETIME=[347FC640:01C2D844]
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tomson Eric (Yahoo.fr) wrote:

>Just three questions :
>
>1/does the IETF support or contest the "Inclusive Name Space" (the one
>operated by NewRoot instead of the ICANN)?
>  
>
RFC-2826 answers this.

-- 
/===========================================================\
|John Stracke      |jstracke@centive.com                    |
|Principal Engineer|http://www.centive.com                  |
|Centive           |My opinions are my own.                 |
|===========================================================|
|A computer without Windows is like a chocolate cake without|
|mustard.                                                   |
\===========================================================/







From owner-ietf@ietf.org  Wed Feb 26 18:18:38 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02344;
	Wed, 26 Feb 2003 18:18:37 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18o9GA-00030h-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 16:38:38 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18m5nV-0001uk-00
	for ietf@ran.ietf.org; Fri, 21 Feb 2003 00:32:33 -0500
Received: from citation.av8.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09952;
	Fri, 21 Feb 2003 00:23:39 -0500 (EST)
Received: from commander.av8.net (IDENT:dean@commander.av8.net [130.105.11.4])
	by citation.av8.net (8.9.3/8.9.3) with ESMTP id AAA14903;
	Fri, 21 Feb 2003 00:24:34 -0500
Date: Fri, 21 Feb 2003 00:25:56 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@commander.av8.net
To: Mark.Andrews@isc.org
cc: mw-list-namedroppers@csi.hu, Name Droppers <namedroppers@ops.ietf.org>,
        <ietf@ietf.org>, <iesg@ietf.org>
Subject: Re: Bind 9 AXFR Modification vs AXFR Clarification 
In-Reply-To: <200302210357.h1L3vr4U010801@drugs.dv.isc.org>
Message-ID: <Pine.LNX.4.44.0302202333060.13516-100000@commander.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:

>
> > On Fri, 21 Feb 2003 Mark.Andrews@isc.org wrote:
> >
> > > > You haven't shown any proof of that.  The "proof" you showed, was the
> > > > result of a misconfiguration.
> > >
> > > 	No.  It is the result of operational reality.  Whenever you
> > > 	have a parent and child zones under different administrative
> > > 	controls it is impossible to change both zones simultaniously.
> > > 	It is also impossible using AXFR or any other mechanism
> > > 	which transfers *individual* zones to transfer them to a
> > > 	secondary and guarantee that they will arrive simultaniously.
> > >
> > > 	Having parent and child zone under different administrative control
> > > 	is the norm not the execption.
> >
> > Actually, a parent always has some control over the child. It exercises
> > this control through the glue records.  When the glue records are in the
> > child zone, they need to be merged.
>
> 	Which is it.  Does the parent control the contents of its zone
> 	or does the child?

You seem not to understand the subtlety of the issue. The parent (like
real parents) ultimately controls the child, but the child (like real
children) has limited autonomy.

> > If a zone transfer happens while they
> > are inconsistent, it is possible for some strange results to happen.
> > Ordinarilly, zone transfers don't happen when they are inconsistent, since
> > the inconsistency is usually short.
>
> 	It doesn't matter if they normally happen while they are
> 	consistant.  You have to get correct behaviour while they
> 	are inconsistant.  Changing zone content on SECONDARY servers
> 	is not correct behaviour.

Sure it is. Unless you can arrange to conduct both updates simultaneosly.
While it would be possible to coordinate such changes on the phone,
relativity could come into play someday.  It has nothing to do with zone
transfers. Its part of the state of the system. Zone transfers is only one
way to learn about the state of the system.

> > Any zone transfers made during the inconsistent window are corrected so
> > long as the child zone is updated with correct information after the
> > parent is updated.
>
> 	This is a incorrect statement.

Could you elaborate?

> > Frequently the parent and child zone are under different administrative
> > control, and are frequently on different servers. In such a case, the
> > contents of the parent zone aren't merged with the child in the child's
> > server, and no evidence of the inconsistency is seen through zone
> > transfers. However, the inconsistency still exists and may still be
> > visible by resolvers and nameservers that lookup the glue records.
>
> 	Nobody is claiming that inconsistancies don't occur all the
> 	time.  What we are claiming is that those inconsistancies
> 	need to be preserved in SECONDARY servers for the correct
> 	operation of the DNS.  That they can only be corrected by
> 	modifying the PRIMARY source of the zones.

???  I can't parse this with respect to your previous statements. Could
you rephrase it?

During the period in which the zone is inconsistent, there is no guarantee
the zone will work.  Depending on the nature of the change, wrong
information may be given in queries as well. Suppose the parent is
removing control from the child, and has updated the glue to remove
referals to the child nameservers. For some time (the TTL, at least), the
original child servers will be queried.

On the other hand, the child zone may not even exist yet on the childs
nameservers.  Referals to the zone fail.

To make a concrete example, Osama registers alquaeda.com, and begins
coordinating his evil deeds. The registrar delegates the alquaeda.com as a
child of .com. Eventually, the government intervenes, and .com replaces
Osamas nameserver glue with new glue pointing to government servers. For a
time, this zone will be inconsistent. Note that in this case, the zone
transfers will not indicate the inconsistency.  However, for a short time,
Osama will be able to put up a message warning his followers not to go to
the government run site. This can't be avoided, no matter what gyrations
you put AXFR through.

It makes no difference that the inconsistency _could_, _in_some_cases_, be
seen at the secondaries.

> > You have obtained no benefits by these constraints.
>
> 	There are clear benefits in preserving zone contents on
> 	SECONDARY servers.

Such as?

Your term "preserving zone contents" is misleading. The zone contents are
not corrupted. The glue is inconsistent.  What is the benefit of
preventing any trace of inconsistency in the secondary?

It has nothing to do with IXFR. It has nothing to do with anything.

> > It is necessary, since the parent has glue records in the child zone.
> > The parent therefore has (always) a part of the child zone. If that server
> > also loads the child zone (or perhaps generates part of it dynamically),
> > it quite reasonable to merge the records as though the zone includes
> > multiple files, which in theory, it does.
>
> 	No it isn't.  Changes need to come from the PRIMARY source not
> 	from intermediate sources.

The intermediate sources aren't making changes. They are, at worst,
propogating old information mixed with new information. However, this is
visible in other ways besides zone transfers.

> > The child zone contents will only be correct when the administrators of
> > both zones agree on the contents of the glue records, and update their
> > parts of the child zone accordingly. It will not be correct until then,
> > regardless of how many zone transfers take place.
>
> 	Which is what I've been saying all along.  It doesn't require
> 	a server to "correct" the content at a intermediate point.  Such
> 	"corrections" actually cause problems.

Good. Then you agree that Bind 8 behavior is correct.

> > > 	Nothing in RFC 1033 / 1034 / 1035 says that a server is permitted
> > > 	to alter the content of a zone.  The responability for maintaining
> > > 	consistancy between zones is a administrative function.
> >
> > This is a loaded statement. The part of the server NOT involved in
> > responding to queries and zone transfers is part of the administrative
> > function. So, as part of that administrative function, it has to be able
> > to modify the RR and zones accordingly.  Your proposed changes exclude a
> > huge part of the potential for intelligence in name servers. And do so
> > with no benefits.
>
> 	The benefits are correct operation of the DNS regardless of the
> 	propogation timings involved.  If servers don't modify slave zone
> 	content then which the master servers are brought into sync all
> 	the servers will be brought into sync.

We already have correct operation of DNS. The zone contents are
inconsistent until both adminstrators come to agreement. The child zone
should be updated last. After the child zone is brought into agreement
with the parent glue, zone transfers will be made which are correct. Only
then will zone transfers will be correct.  Zone transfers made while the
administrators are not in agreement will not be correct, even if there is
no apparent evidence in the zone data from the child (such as a mixture of
new and old glue) they are still incorrect. NS Queries against the parent
and child servers will return different results.

> 	This is not guarenteed if the zone content is modified by a
> 	secondary server.
>
> > > > > > Strange, that was my reaction, too. I'm just trying to be polite.  77
> > %
> > > > > > work just fine. We don't want to break 77% of the servers out there.
> > > > >
> > > > > 	You really think that it will break those servers?  LOL.
> > > >
> > > > They will not be compliant, and thus will need to be changed. Thus, they
> > > > would be broken by definition of not being compliant.
> > >
> > > 	So.  Just because they will not be compliant doesn't mean
> > > 	that that they need to be replaced immediately.  That
> > > 	non-compliance doesn't hurt most of them.  For those where
> > > 	it does have a negative impact it will mean that they should
> > > 	be able to request a fix from their vendor.
> >
> > You seem to make a case that in general, non-compliance doesn't hurt
> > anything. This is false, for both technical and commercial reasons.
> > Technically, it hurts interoperability, which has some many obvious harms
> > I won't go into them. Commercially, implementations make and advertise
> > compatibility and standards compliance claims. This retroactively makes
> > those claims false, which harms the business and reputation of those other
> > vendors.
>
> 	They will be harmed much more if they don't correct a common
> 	error now that it has been pointed out.

Except, there are no errors, beyond a window of inconsistency that cannot
be avoided, and in fact, that window isn't fixed. Nor do you fix the
"error". They are _still_ inconsistent for a period. And the child will
_still_ have to be updated last.

> 	The claims were made in good faith and will be accepted as
> 	such.

I'm not convinced.  If they were, we would have argued this before Bind 9
was released, and before a book was sent out. Probably about 3 years ago.
Someone knew years ago when they wrote the "backward compatibility" mode,
that they had a protocol issue that would have to come before
namedroppers.  That they delayed for so long doesn't indicate good faith
to me.

> > 77% will need a fix from the vendor, if we were to accept these changes.
> >
> > The vendor that made false claims of compatibility and standards
> > compliance is Bind 9. It should suffer the commercial damage to its
> > business and reputation, as a result.
>
> 	BIND 9 conforms to RFC 1034.  Nothing in RFC 1034 says to
> 	merge zone content.  If fact 1034 says that this a administrative
> 	responsability.

It does right now, due to a knowingly reckless exploitation of ambiguity
in the AXFR. Once AXFR is clarified, Bind 9 will have to use its 'backward
compatibility' mode to be compliant.

It is "knowingly reckless" because the Bind 9 implementers _KNEW_ they
needed to provide a "backward compatibility". That means they knew what
they were doing was incompatible with any (all actually) reasonable
interpretation (however ambiguous) of 1034.

> > > > Your failure to comprehend the consequences of the changes does not lesse
> > n
> > > > the effect.  We now agree that these changes aren't necessary to support
> > > > IXFR. You were part of the bad engineering that led to the unnecessary
> > > > creation of these changes in Bind 9.  You were also part of the bad
> > > > decision making that led to the distribution of these changes to Bind 9
> > > > users prior to standardization, and quite possibly you were part of the
> > > > bad decision making that resulted in publishing a book on the subject,
> > > > prior to acceptance of your modifications to standards. In short, you hav
> > e
> > > > shown bad judgement.
> > >
> > > 	I never said that they we not necessary for IXFR.  I said that
> > > 	that your descripition of how to generate the differences was
> > > 	irrelevent to this discussion.
> >
> > Ok, you are half way there. They are irrelevant because IXFR is
> > irrelevant. These changes are not necessary to IXFR, as I explained that
> > IXFR can work with the current AXFR, or even without AXFR.
>
> 	IXFR cannot work through SECONDARY servers that change zone
> 	content regardless of whether the content was learnt via
> 	AXFR or IXFR.

Sure it can.  It doesn't need AXFR at all.  And the secondary's aren't
making arbitrary changes at all.

> > > 	It was bad engineering to merge the data sets together in the
> > > 	first place.  It was not required by RFC 1033/ 1034 / 1035.
> > > 	It had negative consequences.  It was good engineering to
> > > 	correct this.  It was also good engineering to report a
> > > 	common error to the community so that other vendors could
> > > 	fix their mistakes.
> >
> > Actually, since the parent has the glue in the child zone, it has part of
> > the child zone as well as the master zone.  Merging them together is not
> > prohibited, and in the case where child and parent have the same
> > adminstrator, as might be the case where most of the child is simply
> > automatically generated by the nameserver, can make things much easier.
> >
> > Your constraints preclude this unnecessarilly.
>
> 	The constraint in on the SECONDARY server.

So? It is still unnecesary.

> > Since I can think of cases where it is useful to merge records together,
> > it is bad engineering to remove that flexibility and obtain no benefits in
> > return.
> >
> > > > Trying to "belittle" the effects with the "LOL", as opposed to offering
> > > > anything substantive, simply suggests that you have no appreciation of th
> > e
> > > > seriousness of the changes.  Perhaps you should take this more seriously.
> > >
> > > 	I'm quite aware of what the change requires.  I'm also aware
> > > 	that most of the nameserver are used in situations where
> > > 	the zone contents is already preserved because they are not
> > > 	serving zones with parent / child relationships.
> >
> > Apparently, you aren't even aware that your changes will make all non-bind
> > 9 servers non-compliant.  Had you been aware of that, it seems you would
> > have brought this proposal forward something like 3 years ago, before
> > releasing Bind 9, and before publishing a book on the subject.
>
> 	Well you obviously have not been reading.  ISC is not the
> 	only vendor to come to the same conclusion about preserving
> 	zone content.  I suspect that they are just bored with
> 	arguing with you and Dan.

I think they just haven't really read the proposal's, and have taken some
misleading assurances at face value.

> > > 	Anyone saying that all the nameservers need to be replaced
> > > 	immediately is spreading FUD.  LOL the the correct reponse
> > > 	to FUD.
> >
> > Making 77% of the servers non-compliant is a fact of your proposed
> > changes.  It is another fact, as explained, that non-compliant servers
> > will need to be replaced.  Will they suddenly stop working? It depends on
> > whether other implementations want to implement a "backwards
> > compatibility" mode. If they don't implement this mode, then the answer is
> > yes, they will stop working as soon as these updates are deployed by other
> > vendors. Of course, this is a bad result.
>
> 	Well they havn't stopped working in the last two years that
> 	this code has been out there.  Nothing in this drafts stops
> 	a server implementing it taking to any other server.

Uhh, wrong. The drafts make the current AXFR non-compliant. There is
nothing that would require a server to implement the old AXFR and provide
a "backwards compatibility" mode such as Bind 9 has.

So servers running today, won't be able to talk to strictly compliant
servers that don't have a backwards compatibility mode.

> 	There is one backwards compatiblity switch which is only
> 	requires if you decide to send multiple records in a single
> 	messages.  A server is not required to send multiple records
> 	in a single message.

But is allowed to, and a server that can't receive such messages won't be
able to get the zone.

> > > > 1) It doesn't say that it adds a completely new, incompatible zone
> > > > transfer protocol.  New protocols should be made through a different
> > > > process, which includes experimentation. I'm not against experimenting
> > > > with a new protocol. Indeed, I think this idea has some merit. However, i
> > t
> > > > can't be "end-run standardized" by a "clarification". There is a process.
> > >
> > > 	It isn't new.  All it is saying is that the contents tramitted
> > > 	out MUST be that transmitted in.  This occurs most of the time
> > > 	already.  Note BIND is not the only implementation that does
> > > 	this.  We have already had reports of 3 other implementations
> > > 	doing this.  Even the implementations that don't guarentee the
> > > 	contents do this most of the time.  It has no negative effects.
> >
> > No, Section 3.1 is a whole new derivative of AXFR. That is new.
>
> 	Actually it's always been allowed by RFC 1034.  Just because
> 	it wasn't implement initially doesn't mean that it was not
> 	allowed.

Uhh, wrong, except in an unreasonably broad technical exception due to the
vagueness of 1034.

> > > > 4) It doesn't say that it changes the definition of zone data to be
> > > > public. Zone data is absolutely not "public by definition". It could very
> > > > well be useful to tag certain RRs as non-public, and exclude them from
> > > > zone transfers to public servers. This "clarification" precludes that.
> > > > This is really 2 changes.
> > >
> > > 	Nowhere in RFC 1033 / 1034 / 1035 does it say that zone transfers
> > > 	are restricted to secondaries.  Nowhere in RFC 1033 / 1034 / 1035
> > > 	does it say that you should restrict zone tranfers.
> >
> > I don't think you understood my statement. I'm talking about the
> > definition of zone data. Nowhere does 1034 etc say that zone data is
> > public.  It may well have been thought to be public, originally, but since
> > I can easily see a useful purpose in withholding some private RRs, there
> > isn't any reason to preclude that behavior.
>
> 	Does this address your concerns?

No. Because it might be reasonable not to give complete zone data.

>    "The zone transfer protocol allows read-only access to the complete
>    zone data.  When the data being served to the public it is
>    generally acceptable to allow unrestricted access to it via AXFR.
>    Sites that wish to avoid disclosing their full zone data MAY
>    restrict zone transfer access to authorized slaves."
>
> 	If you have part of a zone to which you would normally
> 	return REFUSED to I suggest that you also return REFUSED
> 	to AXFR.
>
> 	If you want to be able to return partial zones then I suggest
> 	that a new TYPE be defined so that receipients can know
> 	that the results will be incomplete.

So far as the secondary is concerned, the zone is complete.  If you do
this, you don't want to tell people that you have some data that isn't
public.  Nor would you ever need to.







From owner-ietf@ietf.org  Wed Feb 26 22:59:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07338;
	Wed, 26 Feb 2003 22:59:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oFBk-0004k1-00
	for ietf-list@ran.ietf.org; Wed, 26 Feb 2003 22:58:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oF91-0004TW-00
	for ietf@ran.ietf.org; Wed, 26 Feb 2003 22:55:39 -0500
Received: from maude.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07217
	for <ietf@ietf.org>; Wed, 26 Feb 2003 22:45:20 -0500 (EST)
Received: from karn by maude.qualcomm.com with local (Exim 3.35 #1 (Debian))
	id 18oF2p-0001JN-00; Wed, 26 Feb 2003 19:49:15 -0800
From: ietf1@ka9q.net
To: ietf@ietf.org
Subject: IAB policy on anti-spam mechanisms?
Reply-to: karn@qualcomm.com
Message-Id: <E18oF2p-0001JN-00@maude.qualcomm.com>
Date: Wed, 26 Feb 2003 19:49:15 -0800
Sender: owner-ietf@ietf.org
Precedence: bulk

I would like to propose that the IAB consider drafting and adopting a
position statement on the highly deleterious effect that certain
anti-spam mechanisms have on legitimate, efficient uses of the
Internet.

I am thinking mainly of the MAPS DUL (Dialup User List), a remarkably
ill-conceived mechanism that complicates life considerably for those
who prefer not to use their ISP's mail servers for reasons of
efficiency, latency and security while doing remarkably little (or
nothing) to actually combat spam.

Here's a page that says better than I can why MAPS DUL is such a bad idea:

http://homepages.tesco.net/~J.deBoynePollard/FGA/maps-dul-is-wrong.html

Other widely deployed but similarly misguided anti-spam mechanisms
include blanket blocks on incoming or outgoing TCP connections to port
25. I've even encountered on ISP that transparently and silently
redirected my outbound SMTP connections to their own mail servers!

All these mechanisms force users to relay outbound or inbound mail
through ISP-run mail servers. This increases latency, decreases
reliability (sometimes substantially), and totally precludes the
effective use of some very useful SMTP security features such as the
AUTH and STARTTLS commands.

There is precedent for the IAB taking a stand on this sort of
thing. In particular, RFC2775 on "Internet Transparency" expresses the
view that the end-to-end principle that underlies the Internet
architecture is still vitally important and worth preserving. Although
RFC2775 spoke mainly to the problems introduced by the widespread use
of NATs, spam filtering is mentioned in passing.

Another relevant precedent is RFC2804, "IETF Policy on Wiretapping",
in which the IETF formally rejected calls to design Internet protocols
to facilitate wiretapping. Yet anti-spam mechanisms that block direct
end-to-end SMTP transfers effectively disables the routine use of
STARTTLS, an automatic, transparent and highly effective
anti-wiretapping mechanism, and makes it a trivial matter for an ISP
to log every email sent or received by its users. At a time of
unprecedented threats to personal privacy and security, the widespread
use of mechanisms like STARTTLS should be encouraged, not discouraged.

As everyone knows, there are many different ideas and approaches to
the spam problem, yet none of them has proven to be a silver
bullet. There is plenty of room for innovation and experimention in
this area, and I certainly wouldn't want to dampen these activities.

However, I believe the IETF and IAB should state some basic principles
that should be observed by everyone working on the spam problem. And
the most basic principle of all should be that no anti-spam mechanism
should ever block email between consenting end-parties without giving
those parties the ability to disable those blocking mechanisms.

As currently implemented, however, end users rarely (if ever) have
such control. They are the "collateral damage" of the spam war, and
are shrugged off just like foreign civilian casualties in most
wars. But a formal policy statement by the IAB or IETF just might give
them something to defend themselves.

Comments?

Phil



From owner-ietf@ietf.org  Thu Feb 27 01:10:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09385;
	Thu, 27 Feb 2003 01:10:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oH7o-0000Hn-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 01:02:32 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oH7S-0000An-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 01:02:10 -0500
Received: from thunker.thunk.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09137
	for <ietf@ietf.org>; Thu, 27 Feb 2003 00:51:49 -0500 (EST)
Received: from [216.175.175.162] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168) 
	(tls_peerdn /C=US/ST=Massachusetts/L=Medford/O=Thunking Systems/OU=SMTP-client/CN=think.thunk.org/Email=tytso@thunk.org)
	 (Exim 3.35 #1 (Debian))
	id 18oH19-0006ID-00; Thu, 27 Feb 2003 00:55:39 -0500
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 18oH18-0008SF-00; Thu, 27 Feb 2003 00:55:38 -0500
Date: Thu, 27 Feb 2003 00:55:38 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: karn@qualcomm.com
Cc: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
Message-ID: <20030227055538.GH24322@think.thunk.org>
References: <E18oF2p-0001JN-00@maude.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E18oF2p-0001JN-00@maude.qualcomm.com>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, Feb 26, 2003 at 07:49:15PM -0800, ietf1@ka9q.net wrote:
> Other widely deployed but similarly misguided anti-spam mechanisms
> include blanket blocks on incoming or outgoing TCP connections to port
> 25. I've even encountered on ISP that transparently and silently
> redirected my outbound SMTP connections to their own mail servers!

Yup, some 802.11 wireless "hotspot" networks block port 25 as well.
Very annoying.  My personal workaround to this is to have a personal
server tucked away at a colo facility, which among other things, runs
a SMTP server listening on port 2025 (to get around the port 25
blocking insanity).  This SMTP server will relay e-mail on my behalf,
no matter when I am in the Internet, after my laptop uses STARTTLS and
AUTH to authenticate myself to my SMTP server.

> As currently implemented, however, end users rarely (if ever) have
> such control. They are the "collateral damage" of the spam war, and
> are shrugged off just like foreign civilian casualties in most
> wars. But a formal policy statement by the IAB or IETF just might give
> them something to defend themselves.

Well as we know, in war, everything is justified, including bombing a
village to save it....   :-(

In any case, if friends/colleagues in the IETF needs a point-defense
against being cannon fodder in the war against SPAM, I can set up
something so they use my forwarding SMTP server when they find
themselves on a subnet being blocked by a silly ISP or on the MAPS DUL
list.  Just let me know so I can set you up with a username/password
pair that will be accepted by my SMTP server.

Of course, this won't help the "little people", but I suppose I'm less
optimistic than you that a recommendation from the IAB will be
effective.  After all, if represenatives from nearly every single
organized religion has signed petitions urging against the war in the
Iraq can be ignored by the George Bush, what makes you think that
anything the IETF or IAB might say will dissuade misguided sysadmins
who hates SPAM more than Bush hates Saddam Hussein....

					- Ted



From owner-ietf@ietf.org  Thu Feb 27 01:43:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09917;
	Thu, 27 Feb 2003 01:43:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oHqH-0007Zq-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 01:48:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oHq5-0007U4-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 01:48:17 -0500
Received: from mxout3.cac.washington.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09813
	for <ietf@ietf.org>; Thu, 27 Feb 2003 01:37:55 -0500 (EST)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R6foAa011297;
	Wed, 26 Feb 2003 22:41:50 -0800
Received: from [192.168.1.125] (p151.n-dapop05.stsn.com [63.241.220.151])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R6fSZI031424
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 26 Feb 2003 22:41:49 -0800
Date: Thu, 27 Feb 2003 00:41:41 -0600 (CST)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@localhost.localdomain
To: "Theodore Ts'o" <tytso@mit.edu>
cc: IETF <ietf@ietf.org>
Subject: Re: IAB policy on anti-spam mechanisms?
In-Reply-To: <20030227055538.GH24322@think.thunk.org>
Message-ID: <Pine.LNX.4.44.0302270033110.3870-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk


On Thu, 27 Feb 2003, Theodore Ts'o wrote:

> On Wed, Feb 26, 2003 at 07:49:15PM -0800, ietf1@ka9q.net wrote:
> > Other widely deployed but similarly misguided anti-spam mechanisms
> > include blanket blocks on incoming or outgoing TCP connections to port
> > 25. I've even encountered on ISP that transparently and silently
> > redirected my outbound SMTP connections to their own mail servers!
>
> Yup, some 802.11 wireless "hotspot" networks block port 25 as well. Very
> annoying.  My personal workaround to this is to have a personal server
> tucked away at a colo facility, which among other things, runs a SMTP
> server listening on port 2025 (to get around the port 25 blocking
> insanity).  This SMTP server will relay e-mail on my behalf, no matter
> when I am in the Internet, after my laptop uses STARTTLS and AUTH to
> authenticate myself to my SMTP server.

Many sites, including my university, support STARTTLS+AUTH on the
Submission port (587, RFC 2476), which I believe is the recommended
service for clients to use to submit mail in any case (though not
well-supported among MUAs, to my knowledge), and also is effective at
getting around ISP blockage of port 25.  Of course if it becomes very
popular the misguided ISPs will block it too.

 - RL "Bob"





From owner-ietf@ietf.org  Thu Feb 27 02:35:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21639;
	Thu, 27 Feb 2003 02:35:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oIbg-0000pZ-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 02:37:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oIbQ-0000je-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 02:37:12 -0500
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21500;
	Thu, 27 Feb 2003 02:26:50 -0500 (EST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h1R7Uih10286;
	Thu, 27 Feb 2003 09:30:44 +0200
Date: Thu, 27 Feb 2003 09:30:44 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: The IESG <iesg-secretary@ietf.org>
cc: Ralph Droms <rdroms@cisco.com>, <ietf@ietf.org>
Subject: Re: WG Action: Dynamic Host Configuration (dhc)
In-Reply-To: <200302262254.RAA00754@ietf.org>
Message-ID: <Pine.LNX.4.44.0302270928280.10075-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Wed, 26 Feb 2003, The IESG wrote:
> A new working group has been formed in the Internet Area of the IETF. 
> For additional information, contact the Area Directors or the Working 
> Group Chairs.

Uhh.. "a new working group"?  What's this old "dhc" working group been,
then, which has operated for years and years?

Was this meant to say that a revised charter has been approved?

> 
> 
> Dynamic Host Configuration (dhc)
> --------------------------------
> 
>      Current Status: Active Working Group
> 
>      Chair(s):
>              R. Droms <rdroms@cisco.com>
> 
>      Internet Area Director(s):
>              Thomas Narten <narten@us.ibm.com>
>              E. Nordmark <erik.nordmark@sun.com>
> 
>      Internet Area Advisor:
>              Thomas Narten <narten@us.ibm.com>
> 
>      Mailing Lists:
>              General Discussion:dhcwg@ietf.org
>              To Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
>              Archive: http://www1.ietf.org/mailman/listinfo/dhcwg
> 
> 
>  Description of Working Group
> 
> 
>  The dhc working group (DHC WG) has developed DHCP for automated
>  allocation, configuration and management of IP addresses and TCP/IP
>  protocol stack parameters. DHCP is currently a "Draft Standard". The
>  base protocol is documented in RFC2131 and RFC2132 (DHCP for IPv4) and
>  RFCxxxx (DHCP for IPv6). Additional options are documented in
>  subsequent RFCs.
> 
>  The DHC WG is responsible for reviewing (and sometimes developing)
>  DHCP options or other extensions (for both IPv4 and IPv6). The DHC WG
>  is expected to review all proposed extensions to DHCP to ensure that
>  they are consistent with the DHCP specification and other option
>  formats, that they do not duplicate existing mechanisms, etc. The DHC
>  WG will not (generally) be responsible for evaluating the semantic
>  content of proposed options. The DHC WG will not adopt new proposals
>  for extensions to DHCP as working group documents without first
>  coordinating with other relevant working groups and determining who
>  has the responsibility for reviewing the semantic content of an
>  option.
> 
>  The DHC WG has the following main objectives:
> 
>  * The DHC WG will address security in DHCP
> 
>        o Develop and document security requirements for DHCP. RFC 3118
>            defines current security mechanisms for DHCPv4. Unfortunately,
>            RFC 3118 has neither been implemented nor deployed to date.
>            Specific issues to be considered include:
> 
>            - Improved key management and scalability
>            - Security for messages passed between relay agents and servers
>            - Threats of DoS attacks through FORCERENEW
>            - The increased usage of DHC on unsecured (e.g., wireless) and
>                public LANs
>            - The need for clients to be able to authenticate servers, without
>                simultaneously requiring client authentication by the server.
> 
>        o Develop and document a roadmap of any new documents or protocols
>            needed to meet the security requirements for DHCP
> 
>  * Write an analysis of the DHCP specification, including RFC2131,
>        RFC2132 and other RFCs defining additional options, which identifies
>        ambiguities, contradictory specifications and other obstacles to
>        development of interoperable implementations. Recommend a process
>        for resolving identified problems and incorporating the resolutions
>        into the DHCP specification.
> 
>  * Complete or abandon work on DHCPv6 options that are currently work
>        in progress:
> 
>            IPv6 Prefix Options for DHCPv6
>                <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
>            DNS Configuration options for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
>            Load Balancing for DHCPv6
>                <draft-ietf-dhc-dhcpv6-loadb-02.txt>
>            NIS Configuration Options for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
>            Time Configuration Options for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
>            Client Preferred Prefix option for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-cliprefprefix-00.txt>
>            A Guide to Implementing Stateless DHCPv6 Service
>                <draft-droms-dhcpv6-stateless-guide-00.txt>
>            DSTM Options for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-dstm-01.txt>
>            DSTM Ports Option for DHCPv6
>                <draft-ietf-dhc-dhcpv6-opt-dstm-ports-01.txt>
> 
>  * Complete or abandon work on DHCP extensions and options that are
>        currently work in progress:
> 
>            Failover protocol
>                <draft-ietf-dhc-failover-11.txt>
>            The DHCP Client FQDN Option
>                <draft-ietf-dhc-fqdn-option-04.txt>
>            Resolution of DNS Name Conflicts Among DHCP Clients
>                <draft-ietf-dhc-ddns-resolution-04.txt>
>            DHCP Server MIB
>                <draft-ietf-dhc-server-mib-07.txt>
>            Considerations for the use of the Host Name option
>                <draft-ietf-dhc-host-option-considerations-01.txt>
>            DHCP Lease Query
>                <draft-ietf-dhc-leasequery-04.txt>
>            DHCP Options for Internet Storage Name Service
>                <draft-ietf-dhc-isnsoption-03.txt>
>            Dynamic Host Configuration Protocol (DHCP) Server MIB
>                <draft-ietf-dhc-server-mib-07.txt>
>            DHCP Option for Mobile IP Mobility Agents
>                <draft-ietf-dhc-mipadvert-opt-00.txt>
>            DHCP VPN Information Option
>                <draft-ietf-dhc-vpn-option-02.txt>
>            KDC Server Address Sub-option
>                <draft-ietf-dhc-suboptions-kdc-serveraddress-00.txt>
>            The Authentication Suboption for the DHCP Relay Agent Option
>                <draft-ietf-dhc-auth-suboption-00.txt>
>            Link Selection sub-option for the Relay Agent Information Option
>                <draft-ietf-dhc-agent-subnet-selection-03.txt>
>            VPN Identifier sub-option for the Relay Agent Information Option
>                <draft-ietf-dhc-agent-vpn-id-02.txt>
>            RADIUS Attributes Sub-option for the DHCP Relay Agent Information Option
>                <draft-ietf-dhc-agentopt-radius-02.txt>
>            DHCP Subscriber ID Suboption for the DHCP Relay Agent Option
>                <draft-ietf-dhc-subscriber-id-00.txt>
> 
>  Milestones (these are to replace the existing ones that are there):
> 
>  Done Resubmit draft-ietf-dhc-dhcpv6-28.txt to IESG
>  Done Identify DHCPv4 authentication design team
>  Done Identify DHCPv4 specification review design team
>  Done Identify DHCPv4 relay agent message authentication design team
>  Done WG Last Call on "DHCP Options for Internet Storage Name Service"
>                        <draft-ietf-dhc-isnsoption-03.txt>
>  Done WG Last Call on "DNS Configuration options for DHCPv6"
>                        <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
>  Done WG Last Call on "NIS Configuration Options for DHCPv6"
>                        <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
>  Done WG Last Call on "Time Configuration Options for DHCPv6"
>                        <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
>  Done WG Last Call on "IPv6 Prefix Options for DHCPv6"
>                        <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
>  Done WG Last Call on "Load Balancing for DHCPv6"
>                        <draft-ietf-dhc-dhcpv6-loadb-02.txt>
>  2003-02 Submit "DHCP Options for Internet Storage Name Service" to IESG
>                        <draft-ietf-dhc-isnsoption-03.txt>
>  2003-02 Submit "DNS Configuration options for DHCPv6" to IESG
>                        <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
>  2003-02 Submit "NIS Configuration Options for DHCPv6" to IESG
>                        <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
>  2003-02 Submit "Time Configuration Options for DHCPv6" to IESG
>                        <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
>  2003-03 Submit "IPv6 Prefix Options for DHCPv6" to IESG
>                        <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
>  2003-03 Submit "Load Balancing for DHCPv6" to IESG
>                        <draft-ietf-dhc-dhcpv6-loadb-02.txt>
>  2003-04 Update milestones to include all WG documents
>  2003-06 DHCPv4 authentication design team report completed
>  2003-06 DHCPv4 specification review report completed
>  2003-06 Select DHCPv4 relay agent message authentication mechanism
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings





From owner-ietf@ietf.org  Thu Feb 27 03:03:49 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22080;
	Thu, 27 Feb 2003 03:03:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oJ3m-00044A-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 03:06:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oJ2z-0003xb-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 03:05:41 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21961
	for <ietf@ietf.org>; Thu, 27 Feb 2003 02:55:20 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 909C86258E
	for <ietf@ietf.org>; Thu, 27 Feb 2003 08:59:12 +0100 (CET)
Date: Thu, 27 Feb 2003 15:27:56 +0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Posting statistics for the IETF list
Message-ID: <59138256.1046359676@localhost>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Top posters to the IETF list, for the period of Jan 21 to Feb 26:

  1   23   8.13 "D. J. Bernstein" <djb@cr.yp.to>
  2   19  14.84 Mark.Andrews@isc.org
  3   17  20.85 Dean Anderson <dean@av8.com>
  4   13  25.44 Harald Tveit Alvestrand <harald@alvestrand.no>
  5   10  28.98 "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
  6    9  32.16 Robert Elz <kre@munnari.OZ.AU>
  7    9  35.34 John C Klensin <john-ietf@jck.com>

No comment.




From owner-ietf@ietf.org  Thu Feb 27 03:18:01 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22528;
	Thu, 27 Feb 2003 03:18:01 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oJKE-0006F5-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 03:23:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oJGb-0005qL-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 03:19:45 -0500
Received: from net.cc.swin.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22224
	for <ietf@ietf.org>; Thu, 27 Feb 2003 03:09:23 -0500 (EST)
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by net.cc.swin.edu.au (8.9.3/8.9.3) with ESMTP id TAA17022;
	Thu, 27 Feb 2003 19:13:16 +1100 (AEDT)
Message-ID: <3E5DC89C.FBDC04CA@swin.edu.au>
Date: Thu, 27 Feb 2003 19:13:16 +1100
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Posting statistics for the IETF list
References: <59138256.1046359676@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Harald Tveit Alvestrand wrote:
> 
> Top posters to the IETF list, for the period of Jan 21 to Feb 26:
	[..]
> No comment.

Perhaps you should. Comment on whether this will become a regular
thing, whether the 21st of one month to the 26th of the next will
be a regular sample interval, or whether there was some other point
you really wanted to make. There are a number of conclusions we could
draw in the absence of proper guidance.

gja



From owner-ietf@ietf.org  Thu Feb 27 06:18:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25433;
	Thu, 27 Feb 2003 06:18:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oM5V-0007r4-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 06:20:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oM4p-0007kT-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 06:19:47 -0500
Received: from rtp-core-2.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25174;
	Thu, 27 Feb 2003 06:09:22 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h1RBDHNh010889;
	Thu, 27 Feb 2003 06:13:17 -0500 (EST)
Received: from rdroms-w2k.cisco.com (sjc-vpn4-59.cisco.com [10.21.80.59]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA24700; Thu, 27 Feb 2003 06:13:12 -0500 (EST)
Message-Id: <4.3.2.7.2.20030227061152.03dad888@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 27 Feb 2003 06:13:10 -0500
To: The IESG <iesg-secretary@ietf.org>, <ietf@ietf.org>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: WG Action: Dynamic Host Configuration (dhc)
In-Reply-To: <Pine.LNX.4.44.0302270928280.10075-100000@netcore.fi>
References: <200302262254.RAA00754@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

All,


Yes ... the announcement in question should have read "recharter",
not "new working group".

- Ralph

At 09:30 AM 2/27/2003 +0200, Pekka Savola wrote:
>On Wed, 26 Feb 2003, The IESG wrote:
> > A new working group has been formed in the Internet Area of the IETF.
> > For additional information, contact the Area Directors or the Working
> > Group Chairs.
>
>Uhh.. "a new working group"?  What's this old "dhc" working group been,
>then, which has operated for years and years?
>
>Was this meant to say that a revised charter has been approved?
>
> >
> >
> > Dynamic Host Configuration (dhc)
> > --------------------------------
> >
> >      Current Status: Active Working Group
> >
> >      Chair(s):
> >              R. Droms <rdroms@cisco.com>
> >
> >      Internet Area Director(s):
> >              Thomas Narten <narten@us.ibm.com>
> >              E. Nordmark <erik.nordmark@sun.com>
> >
> >      Internet Area Advisor:
> >              Thomas Narten <narten@us.ibm.com>
> >
> >      Mailing Lists:
> >              General Discussion:dhcwg@ietf.org
> >              To Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
> >              Archive: http://www1.ietf.org/mailman/listinfo/dhcwg
> >
> >
> >  Description of Working Group
> >
> >
> >  The dhc working group (DHC WG) has developed DHCP for automated
> >  allocation, configuration and management of IP addresses and TCP/IP
> >  protocol stack parameters. DHCP is currently a "Draft Standard". The
> >  base protocol is documented in RFC2131 and RFC2132 (DHCP for IPv4) and
> >  RFCxxxx (DHCP for IPv6). Additional options are documented in
> >  subsequent RFCs.
> >
> >  The DHC WG is responsible for reviewing (and sometimes developing)
> >  DHCP options or other extensions (for both IPv4 and IPv6). The DHC WG
> >  is expected to review all proposed extensions to DHCP to ensure that
> >  they are consistent with the DHCP specification and other option
> >  formats, that they do not duplicate existing mechanisms, etc. The DHC
> >  WG will not (generally) be responsible for evaluating the semantic
> >  content of proposed options. The DHC WG will not adopt new proposals
> >  for extensions to DHCP as working group documents without first
> >  coordinating with other relevant working groups and determining who
> >  has the responsibility for reviewing the semantic content of an
> >  option.
> >
> >  The DHC WG has the following main objectives:
> >
> >  * The DHC WG will address security in DHCP
> >
> >        o Develop and document security requirements for DHCP. RFC 3118
> >            defines current security mechanisms for DHCPv4. Unfortunately,
> >            RFC 3118 has neither been implemented nor deployed to date.
> >            Specific issues to be considered include:
> >
> >            - Improved key management and scalability
> >            - Security for messages passed between relay agents and servers
> >            - Threats of DoS attacks through FORCERENEW
> >            - The increased usage of DHC on unsecured (e.g., wireless) and
> >                public LANs
> >            - The need for clients to be able to authenticate servers, 
> without
> >                simultaneously requiring client authentication by the 
> server.
> >
> >        o Develop and document a roadmap of any new documents or protocols
> >            needed to meet the security requirements for DHCP
> >
> >  * Write an analysis of the DHCP specification, including RFC2131,
> >        RFC2132 and other RFCs defining additional options, which identifies
> >        ambiguities, contradictory specifications and other obstacles to
> >        development of interoperable implementations. Recommend a process
> >        for resolving identified problems and incorporating the resolutions
> >        into the DHCP specification.
> >
> >  * Complete or abandon work on DHCPv6 options that are currently work
> >        in progress:
> >
> >            IPv6 Prefix Options for DHCPv6
> >                <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
> >            DNS Configuration options for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
> >            Load Balancing for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-loadb-02.txt>
> >            NIS Configuration Options for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
> >            Time Configuration Options for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
> >            Client Preferred Prefix option for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-cliprefprefix-00.txt>
> >            A Guide to Implementing Stateless DHCPv6 Service
> >                <draft-droms-dhcpv6-stateless-guide-00.txt>
> >            DSTM Options for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-dstm-01.txt>
> >            DSTM Ports Option for DHCPv6
> >                <draft-ietf-dhc-dhcpv6-opt-dstm-ports-01.txt>
> >
> >  * Complete or abandon work on DHCP extensions and options that are
> >        currently work in progress:
> >
> >            Failover protocol
> >                <draft-ietf-dhc-failover-11.txt>
> >            The DHCP Client FQDN Option
> >                <draft-ietf-dhc-fqdn-option-04.txt>
> >            Resolution of DNS Name Conflicts Among DHCP Clients
> >                <draft-ietf-dhc-ddns-resolution-04.txt>
> >            DHCP Server MIB
> >                <draft-ietf-dhc-server-mib-07.txt>
> >            Considerations for the use of the Host Name option
> >                <draft-ietf-dhc-host-option-considerations-01.txt>
> >            DHCP Lease Query
> >                <draft-ietf-dhc-leasequery-04.txt>
> >            DHCP Options for Internet Storage Name Service
> >                <draft-ietf-dhc-isnsoption-03.txt>
> >            Dynamic Host Configuration Protocol (DHCP) Server MIB
> >                <draft-ietf-dhc-server-mib-07.txt>
> >            DHCP Option for Mobile IP Mobility Agents
> >                <draft-ietf-dhc-mipadvert-opt-00.txt>
> >            DHCP VPN Information Option
> >                <draft-ietf-dhc-vpn-option-02.txt>
> >            KDC Server Address Sub-option
> >                <draft-ietf-dhc-suboptions-kdc-serveraddress-00.txt>
> >            The Authentication Suboption for the DHCP Relay Agent Option
> >                <draft-ietf-dhc-auth-suboption-00.txt>
> >            Link Selection sub-option for the Relay Agent Information Option
> >                <draft-ietf-dhc-agent-subnet-selection-03.txt>
> >            VPN Identifier sub-option for the Relay Agent Information Option
> >                <draft-ietf-dhc-agent-vpn-id-02.txt>
> >            RADIUS Attributes Sub-option for the DHCP Relay Agent 
> Information Option
> >                <draft-ietf-dhc-agentopt-radius-02.txt>
> >            DHCP Subscriber ID Suboption for the DHCP Relay Agent Option
> >                <draft-ietf-dhc-subscriber-id-00.txt>
> >
> >  Milestones (these are to replace the existing ones that are there):
> >
> >  Done Resubmit draft-ietf-dhc-dhcpv6-28.txt to IESG
> >  Done Identify DHCPv4 authentication design team
> >  Done Identify DHCPv4 specification review design team
> >  Done Identify DHCPv4 relay agent message authentication design team
> >  Done WG Last Call on "DHCP Options for Internet Storage Name Service"
> >                        <draft-ietf-dhc-isnsoption-03.txt>
> >  Done WG Last Call on "DNS Configuration options for DHCPv6"
> >                        <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
> >  Done WG Last Call on "NIS Configuration Options for DHCPv6"
> >                        <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
> >  Done WG Last Call on "Time Configuration Options for DHCPv6"
> >                        <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
> >  Done WG Last Call on "IPv6 Prefix Options for DHCPv6"
> >                        <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
> >  Done WG Last Call on "Load Balancing for DHCPv6"
> >                        <draft-ietf-dhc-dhcpv6-loadb-02.txt>
> >  2003-02 Submit "DHCP Options for Internet Storage Name Service" to IESG
> >                        <draft-ietf-dhc-isnsoption-03.txt>
> >  2003-02 Submit "DNS Configuration options for DHCPv6" to IESG
> >                        <draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt>
> >  2003-02 Submit "NIS Configuration Options for DHCPv6" to IESG
> >                        <draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt>
> >  2003-02 Submit "Time Configuration Options for DHCPv6" to IESG
> >                        <draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt>
> >  2003-03 Submit "IPv6 Prefix Options for DHCPv6" to IESG
> >                        <draft-troan-dhcpv6-opt-prefix-delegation-02.txt>
> >  2003-03 Submit "Load Balancing for DHCPv6" to IESG
> >                        <draft-ietf-dhc-dhcpv6-loadb-02.txt>
> >  2003-04 Update milestones to include all WG documents
> >  2003-06 DHCPv4 authentication design team report completed
> >  2003-06 DHCPv4 specification review report completed
> >  2003-06 Select DHCPv4 relay agent message authentication mechanism
> >
>
>--
>Pekka Savola                 "You each name yourselves king, yet the
>Netcore Oy                    kingdom bleeds."
>Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-ietf@ietf.org  Thu Feb 27 10:50:50 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08789;
	Thu, 27 Feb 2003 10:50:49 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oPyR-0007ve-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 10:29:27 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oPCe-0007SV-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 09:40:04 -0500
Received: from thunker.thunk.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05149
	for <ietf@ietf.org>; Thu, 27 Feb 2003 09:29:38 -0500 (EST)
Received: from [216.175.175.162] (helo=think.thunk.org)
	authenticated as tytso by thunker.thunk.org with asmtp 
	(tls_cipher TLSv1:DES-CBC3-SHA:168) 
	(tls_peerdn /C=US/ST=Massachusetts/L=Medford/O=Thunking Systems/OU=SMTP-client/CN=think.thunk.org/Email=tytso@thunk.org)
	 (Exim 3.35 #1 (Debian))
	id 18oP5v-0001uF-00; Thu, 27 Feb 2003 09:33:07 -0500
Received: from tytso authenticated as tytso by think.thunk.org with local   (Exim 3.35 #1 (Debian))
	id 18oP5u-0000k7-00; Thu, 27 Feb 2003 09:33:06 -0500
Date: Thu, 27 Feb 2003 09:33:06 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
Cc: IETF <ietf@ietf.org>
Subject: Re: IAB policy on anti-spam mechanisms?
Message-ID: <20030227143306.GM24322@think.thunk.org>
References: <20030227055538.GH24322@think.thunk.org> <Pine.LNX.4.44.0302270033110.3870-100000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0302270033110.3870-100000@localhost.localdomain>
User-Agent: Mutt/1.4i
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, Feb 27, 2003 at 12:41:41AM -0600, RL 'Bob' Morgan wrote:
> Many sites, including my university, support STARTTLS+AUTH on the
> Submission port (587, RFC 2476), which I believe is the recommended
> service for clients to use to submit mail in any case (though not
> well-supported among MUAs, to my knowledge), and also is effective at
> getting around ISP blockage of port 25.  Of course if it becomes very
> popular the misguided ISPs will block it too.

Yup, the problem with well-known ports is that well-known port numbers
get either (a) blocked by misguded ISP's, or (b) transparently proxed
by misguided ISP's.  Since I have no idea what sort of stupidity I
might encounter at various different hotel, conference, or 802.11
hotspot networks, it's more convenient for me to use a non-standard
port.

The MUA issue isn't important in my case, because I run a local MTA on
my latop (exim), which is configured to do the STARTTLS and AUTH, so I
can use any MUA I wish.

						- Ted



From owner-ietf@ietf.org  Thu Feb 27 11:09:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09639;
	Thu, 27 Feb 2003 11:09:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oQHR-0001Jv-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 10:49:05 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oPxp-0007hz-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 10:28:49 -0500
Received: from mail.asianet.co.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07652
	for <ietf@ietf.org>; Thu, 27 Feb 2003 10:18:21 -0500 (EST)
Message-Id: <200302271518.KAA07652@ietf.org>
Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.198])
          (envelope-sender <jrace@attglobal.net>)
          by mail1.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 27 Feb 2003 22:22:38 +0700
Received: from ppp-203.144.203.60.revip.asianet.co.th (HELO localhost) ([203.144.203.60])
          (envelope-sender <jrace@attglobal.net>)
          by mx2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 27 Feb 2003 22:12:51 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>, "karn@qualcomm.com" <karn@qualcomm.com>
Date: Thu, 27 Feb 2003 22:22:03 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: IAB policy on anti-spam mechanisms?
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Phil et al, pls see inline comments.  I am preparing a detailed
proposal on a related issue (releasing draft in a few days) and would 
welcome your replies so as to incorporate inputs as appropriate.

On Wed, 26 Feb 2003 19:49:15 -0800, ietf1@ka9q.net wrote:
>I would like to propose that the IAB consider drafting and adopting a
>position statement on the highly deleterious effect that certain
>anti-spam mechanisms have on legitimate, efficient uses of the
>Internet.
>>I am thinking mainly of the MAPS DUL (Dialup User List), a remarkably
>ill-conceived mechanism that complicates life considerably for those
>who prefer not to use their ISP's mail servers for reasons of
>efficiency, latency and security while doing remarkably little (or
>nothing) to actually combat spam.

It seems there's a need to balance interests among different groups of
users.   What is your proposed solution to prevent emission of
spam via dialup, if you propose to discourage the DUL?  (My
proposal imposes a positive duty of care of ISPs to prevent
emission of spam, so I am quite concerned about this.)


[snip]
 which the IETF formally rejected calls to design Internet protocols
>to facilitate wiretapping. Yet anti-spam mechanisms that block direct
>end-to-end SMTP transfers effectively disables the routine use of
>STARTTLS, an automatic, transparent and highly effective
>anti-wiretapping mechanism, and makes it a trivial matter for an ISP
>to log every email sent or received by its users.

Behavioral Studies 1 teaches that responsibility is ensured only
by accountability, and accountability entails traceability.  What
is your alternative to ensure traceability for abusive transmissions?


[snip]

>However, I believe the IETF and IAB should state some basic principles
>that should be observed by everyone working on the spam problem. And
>the most basic principle of all should be that no anti-spam mechanism
>should ever block email between consenting end-parties without giving
>those parties the ability to disable those blocking mechanisms.

Could you explain this please?   The difficulty I foresee is that
ISPs are under legal obligations to prevent their property from being
abused to injure others.  (Unfortunately many ISPs don't fulfill
their obligation diligently as of now, but that is another story.)
If the ISP chooses system-wide blocking, how could it be disabled
on a per-user basis without facilitating spamming?

>
>As currently implemented, however, end users rarely (if ever) have
>such control. They are the "collateral damage" of the spam war, and
>are shrugged off just like foreign civilian casualties in most
>wars. But a formal policy statement by the IAB or IETF just might give
>them something to defend themselves.

Well in fact collateral damage is the ONLY THING that motivates
certain scum ISPs to reform, as has been repeatedly proven.  I can
give you the cites if you like.   So collateral damage may have to
be viewed as an interim necessity given the low ethical standards
of some of the leading firms in the industry.

>Comments?

 Poof! There they are!

Jeffrey Race





From owner-ietf@ietf.org  Thu Feb 27 11:16:45 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09889;
	Thu, 27 Feb 2003 11:16:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oQn1-0003gf-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 11:21:43 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oQUl-0002EJ-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 11:02:51 -0500
Received: from dhcp-168-17-124.autonomica.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08941
	for <ietf@ietf.org>; Thu, 27 Feb 2003 10:52:24 -0500 (EST)
Received: from kurtis.pp.se (localhost [127.0.0.1])
	by dhcp-168-17-124.autonomica.se (8.12.6/8.10.2) with ESMTP id h1RFvZif009858;
	Thu, 27 Feb 2003 16:57:37 +0100 (CET)
Date: Thu, 27 Feb 2003 16:57:35 +0100
Subject: Re: Posting statistics for the IETF list
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: ietf@ietf.org
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
In-Reply-To: <59138256.1046359676@localhost>
Message-Id: <2FD84924-4A6C-11D7-ADF5-000393AB1404@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> No comment.
>

That the IETF list has taken over as discussion list for DNS related 
discussions instead of namedroppers?

- kurtis -




From owner-ietf@ietf.org  Thu Feb 27 11:58:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11384;
	Thu, 27 Feb 2003 11:58:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oRIo-0007xD-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 11:54:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oRFu-0007cd-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 11:51:34 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10815
	for <ietf@ietf.org>; Thu, 27 Feb 2003 11:41:06 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h1RGiwoF015688
	for ietf@ietf.org env-from <vjs>;
	Thu, 27 Feb 2003 09:44:58 -0700 (MST)
Date: Thu, 27 Feb 2003 09:44:58 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200302271644.h1RGiwoF015688@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Posting statistics for the IETF list
References: <2FD84924-4A6C-11D7-ADF5-000393AB1404@kurtis.pp.se>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>

> > No comment.
>
> That the IETF list has taken over as discussion list for DNS related 
> discussions instead of namedroppers?

Didn't it start with something about a last-call?  If so, it served
to resolve lingering doubts and crystalize consensus.

That it is so similar to previous rounds such as the TAP/IDENT "debate"
is probably irrelevant.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 27 12:15:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12156;
	Thu, 27 Feb 2003 12:15:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oRhy-0002N1-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 12:20:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oRhB-0002EQ-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 12:19:45 -0500
Received: from sleekfreak.ath.cx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11890
	for <ietf@ietf.org>; Thu, 27 Feb 2003 12:09:17 -0500 (EST)
Received: from localhost ([127.0.0.1] ident=shogunx)
	by sleekfreak.ath.cx with esmtp (Exim 3.35 #1 (Debian))
	id 18oFQM-0001aW-00; Wed, 26 Feb 2003 23:13:34 -0500
Date: Wed, 26 Feb 2003 23:13:33 -0500 (EST)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: john smith <johnsmith0302@hotmail.com>
cc: ietf@ietf.org
Subject: Re: cables
In-Reply-To: <OE15OgRGkQ6mBySsxVY00008a4c@hotmail.com>
Message-ID: <Pine.LNX.4.44.0302262312580.6064-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Thu, 20 Feb 2003, john smith wrote:

>
> on ethernet,
>
>
> If all ports were DTE pin configured (same pair everywhere for rx and tx)
>
> and all cables were cross
>
> life would be simpler.

I once built a network using nothing but cross-connects.  It was nice.

Scott

>
> -JS
>
>
>
>
>

sleekfreak pirate broadcast
world tour 2002-3
live from daytona beach
http://sleekfreak.ath.cx




From owner-ietf@ietf.org  Thu Feb 27 12:15:40 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12189;
	Thu, 27 Feb 2003 12:15:40 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oRhz-0002N7-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 12:20:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oRhW-0002EV-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 12:20:06 -0500
Received: from ccr.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11905
	for <ietf@ietf.org>; Thu, 27 Feb 2003 12:09:38 -0500 (EST)
Received: from ccr.org (localhost [127.0.0.1])
	by ccr.org (8.9.2/8.11.0) with ESMTP id MAA09401;
	Thu, 27 Feb 2003 12:13:28 -0500 (EST)
	(envelope-from mo@ccr.org)
Message-Id: <200302271713.MAA09401@ccr.org>
To: "Theodore Ts'o" <tytso@mit.edu>
cc: "RL 'Bob' Morgan" <rlmorgan@washington.edu>, IETF <ietf@ietf.org>
Subject: Re: IAB policy on anti-spam mechanisms? 
In-reply-to: Your message of "Thu, 27 Feb 2003 09:33:06 EST."
             <20030227143306.GM24322@think.thunk.org> 
Date: Thu, 27 Feb 2003 12:13:28 -0500
From: "Mike O'Dell" <mo@ccr.org>
Sender: owner-ietf@ietf.org
Precedence: bulk


i think you'll find that port 25 is blocked going anywhere except
the operator's outgoing MTA

this is to require authentication to send email, exercise rate
limiting, and other anti-spam-sending strategies

if the ISP is going to be held responsible for the behavior of
their clients, then the ISPs are going to take some action to
police that behavior

note i'm not suggesting this is a good idea, just that it's what has
happened given the current reality

there is a huge disconnect here.  one camp claims that mail sending
should not be allowed by just "anyone", since that ability is
instantly abused by Bad Guys.  another camp claims that forcing email
through alien MTAs is a violation of the end-to-end principle,
privacy, assorted other good ideas.

both are right at some level

there *is* no notion of "strong identity" in the network world today
and i know of no serious attempt to create one, probably for good
reasons

this means that actions on the Internet are inherently anonymous, or
at least unaccountable because the only "identity" arises from a
contractual business relationship between a person and an access
provider.  the access provider is therefore held to be a proxy for
the individual since he does (or at least should, at some level)
have a role in allowing that individual to take various actions.

one major source of the problem is the ease in which Internet access
is available.  one can get a dial-up account quite readily and the
credentials required are trivial to acquired, especially for someone
determined to acquire them.  

so if a Bad Guy acquires access, he can do a lot in the amount of
time required for the business feedback loop to deny access and
cancel the account.  in the mean time, the Bad Guy has acquired
numerous other accounts and when one fails, he just starts using
a new one.  

This is essentially a "disposable identity". The identity is the
binding inherent in the business relationship with an access provider,
and when it becomes worthless, it is discarded and a new one is used.

A consequence of the ease with which credentials can be acquired is
the ease with which new accounts, and hence new identities, can
be acquired.  

To fix this at the "source", so to speak, it would require
making access *much* harder to get.  simply matching credit cards,
etc, is insufficient (credit cards are easy to get), so this leads
to a world where some kind of background check would be required.

I don't think anyone wants to pursue that. (at least seriously)

So what's left?  

As I said earlier, the alternative is to provide the ability to
intercede in network behavior fast enough to have any effectiveness.
This generally means preventing sending email without some form
of vetting.  This usually means authentication and then some
additional behavioral control on top of it.  Rate-based models seem
to be the least intrusive.  They allow people doing "real people"
things to proceed with essentially zero interference while spam
senders are thwarted to some significant effect.  If a client
has a real need to have the behavior limits altered, the provider
can enter into an addendum to the service agreement.  this still
provides for a degree of behavior monitoring to police the impact
on the rest of the network.

I will end by noting that many people are in both of the camps
described above - they want a "throat to choke" proxy for individual
behavior, but they want unimpeded ability to send email themselves.

while I agree with the desire, it is self-contradictory.

	-mo



From owner-ietf@ietf.org  Thu Feb 27 13:01:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14235;
	Thu, 27 Feb 2003 13:01:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oSKr-0000KI-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 13:00:45 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oSFO-00083s-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 12:55:06 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13674
	for <ietf@ietf.org>; Thu, 27 Feb 2003 12:44:36 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h1RHmVPa023374
	for ietf@ietf.org env-from <vjs>;
	Thu, 27 Feb 2003 10:48:31 -0700 (MST)
Date: Thu, 27 Feb 2003 10:48:31 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200302271748.h1RHmVPa023374@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
References:  <200302271713.MAA09401@ccr.org
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: "Mike O'Dell" <mo@ccr.org>

> i think you'll find that port 25 is blocked going anywhere except
> the operator's outgoing MTA

Only by the slumlord ISPs.


> this is to require authentication to send email, exercise rate
> limiting, and other anti-spam-sending strategies

Or so they say.

> if the ISP is going to be held responsible for the behavior of
> their clients, then the ISPs are going to take some action to
> police that behavior
> ...

Blocking port 25 is equivalent to replacing glass windows with Lexan
and putting razor wire fences around your tenement in order to control
bad tenents instead of policing them.  Both are a lot cheaper than
enforcing good behavior including making enough examples to deter it.

UUNet in particular has demonstrated this sad syndrome.  For years,
instead of ejecting its spamming and spam-friendly resellers, it lied.
Then it lied for years about installing port 25 filtering.  Finally,
it got port 25 filtering working, and reduced the amount of dial-up
spam it was spewing.  All of that was instead of enforcing an anti-spam
AUP and genuinely cracking down on spammers.  (By "lies" I mean official
public statements in news.admin.net-abuse.email and to individuals that
the UUnet spokesmen could not possibly have failed to know were false.)

Of course, UUNet is far from the only example.  Another good one is
Sprint, which had the audacity to claim to not know how to use ANI to
find spammers running up 5-figure bills on stolen credit numbers or
how to interest law enforcement agencies....this from a telco!


> there is a huge disconnect here.  one camp claims that mail sending
> should not be allowed by just "anyone", since that ability is
> instantly abused by Bad Guys.  another camp claims that forcing email
> through alien MTAs is a violation of the end-to-end principle,
> privacy, assorted other good ideas.
>
> both are right at some level

That first is how it is seen by spam-friendly ISPs, ISPs that want to
cram the Internet back into the ancient AOL/Genie/etc users-with-dumb-
terminals model, and assorted people who like to fight with spammers.
All three groups have reasons for ignoring the fact that outgoing spam
is not a major problem among ISPs that honestly enforce anti-spam AUPs.


> ...
> this means that actions on the Internet are inherently anonymous, or
> at least unaccountable because the only "identity" arises from a
> contractual business relationship between a person and an access
> provider.  the access provider is therefore held to be a proxy for
> the individual since he does (or at least should, at some level)
> have a role in allowing that individual to take various actions.

And it is cheaper for service providers to prohibit SMTP than to break
some financial kneecaps to convince spammers to use spam-friendly ISPs.


> ...
> so if a Bad Guy acquires access, he can do a lot in the amount of
> time required for the business feedback loop to deny access and
> cancel the account.  in the mean time, the Bad Guy has acquired
> numerous other accounts and when one fails, he just starts using
> a new one.  

Yes, and if the ISP does no more than cancel the account, we have
examples such as Netcom's special spam-for-a-day rates.  Of course,
Netcom was not the first and certainly won't be the last to cater to
the spam-for-a-day business.

> This is essentially a "disposable identity". The identity is the
> binding inherent in the business relationship with an access provider,
> and when it becomes worthless, it is discarded and a new one is used.

That's what the slumlord ISPs claim, but we all know it's false.
Except for stolen credit cards, the identities associate with credit
cards are not that disposable or anonymous.


> A consequence of the ease with which credentials can be acquired is
> the ease with which new accounts, and hence new identities, can
> be acquired.  
>
> To fix this at the "source", so to speak, it would require
> making access *much* harder to get.  simply matching credit cards,
> etc, is insufficient (credit cards are easy to get), so this leads
> to a world where some kind of background check would be required.
> ...

If that were true, then credit card purchases of merchandise would
be hopeless.   Even "bricks-and-mortar" credit card transactions would
involve too much fraud to be tolerable.

There's no reason ISPs cannot use the same sort of fraud prevention
mechanisms used by other online merchants.  For example, there are
equilvents to matching credit card shipping and billing addresses such
as requiring a new customer to sign a contract and return it by paper
mail (including terms of service that impose significant penalties
for abuse).  The problem with such measures is that the are not free.
It's cheaper to put up the razor wire fences around the tenements.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf@ietf.org  Thu Feb 27 14:20:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17652;
	Thu, 27 Feb 2003 14:20:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oTb4-0003Tx-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 14:21:34 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oTZy-0003AV-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 14:20:26 -0500
Received: from episteme-software.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17430
	for <ietf@ietf.org>; Thu, 27 Feb 2003 14:09:56 -0500 (EST)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server 3.2b5);
 Thu, 27 Feb 2003 13:14:14 -0600
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com
Message-Id: <p06000808ba8413027bfa@[216.43.25.67]>
In-Reply-To: <E18oF2p-0001JN-00@maude.qualcomm.com>
References: <E18oF2p-0001JN-00@maude.qualcomm.com>
X-Mailer: Eudora [Macintosh version 6.0a8]
Date: Thu, 27 Feb 2003 13:13:50 -0600
To: karn@qualcomm.com
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: IAB policy on anti-spam mechanisms?
Cc: ietf@ietf.org, ietf1@ka9q.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

On 2/26/03 at 7:49 PM -0800, Phil Karn wrote:

>I would like to propose that the IAB consider drafting and adopting 
>a position statement on the highly deleterious effect that certain 
>anti-spam mechanisms have on legitimate, efficient uses of the 
>Internet.

It seems to me that this is a perfect topic to be discussed at the 
Thursday morning Anti-Spam IRTF group meeting.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated



From owner-ietf@ietf.org  Thu Feb 27 14:39:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18561;
	Thu, 27 Feb 2003 14:39:24 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oTuS-00074l-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 14:41:36 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oTtL-0006hH-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 14:40:27 -0500
Received: from noxmail.sandelman.ottawa.on.ca (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18166
	for <ietf@ietf.org>; Thu, 27 Feb 2003 14:29:57 -0500 (EST)
Received: from sandelman.ottawa.on.ca ([2002:c08b:2e21:2:204:76ff:fe2d:8c])
	by noxmail.sandelman.ottawa.on.ca (8.11.6/8.11.6) with ESMTP id h1RJXqv16810
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK)
	for <ietf@ietf.org>; Thu, 27 Feb 2003 14:33:54 -0500 (EST)
Received: from marajade.sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h1RJXoFp025963
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK)
	for <ietf@ietf.org>; Thu, 27 Feb 2003 14:33:52 -0500
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by marajade.sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian -4) with ESMTP id h1RJXnNw025959
	for <ietf@ietf.org>; Thu, 27 Feb 2003 14:33:49 -0500
Message-Id: <200302271933.h1RJXnNw025959@marajade.sandelman.ottawa.on.ca>
To: IETF <ietf@ietf.org>
Subject: Re: IAB policy on anti-spam mechanisms? 
In-reply-to: Your message of "Thu, 27 Feb 2003 12:13:28 EST."
             <200302271713.MAA09401@ccr.org> 
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 27 Feb 2003 14:33:48 -0500
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Sender: owner-ietf@ietf.org
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----


The "nicest" solution that I can see is for the ISPs to transparently
proxy port 25 to their MTA. They should offer STARTTLS.

If the client selects STARTTLS, their proxy should immediately connect
directly to the intended destination, permitting the connection to go
through. May well let the clueful through.  This could be open to further
abuse, as you can't tell what the client/server are doing now.

However, the ISP still gets to rate limit the number of connections
that the client makes. This in itself is probably very powerful.

Things that IETF clueful road warriors can do, and I do:
       1) use IPsec to your mail relay.	I do this automatically.
       2) use IPv6 (always configure 6to4 on your notebook)

I then, as Ted does, do authenticated relaying with STARTTLS. 

So, my packets look like:
    SMTP/TLS/TCP/IPv6/IPv4-encap-v6/IPsec/IPv4.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPl5oGYqHRg3pndX9AQFQaAP9HvRH2pvQt04TvuTzfw2QzLKwMFX5XNkG
Tsdf7eqMhBaPvm0qKKYdd43NA3UHOHBu1I25iVuCv0eFU5iFfwZNE7TOG0CdYcoX
mW5Oet6eKDG+FfVC/QWBTrk2ZsVy3tEGP96OIodOaIMsbZNNgTkWtyzDA1izWRza
Hej1CaN4Mts=
=fbft
-----END PGP SIGNATURE-----



From owner-ietf@ietf.org  Thu Feb 27 16:29:30 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24590;
	Thu, 27 Feb 2003 16:29:30 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oVbC-000309-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 16:29:50 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oVXN-0001tB-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 16:25:53 -0500
Received: from joy.songbird.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24078
	for <ietf@ietf.org>; Thu, 27 Feb 2003 16:15:20 -0500 (EST)
Received: from rshockeybox.shockey.us (inetgw.va.neustar.com [209.173.53.225])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id NAA07424;
	Thu, 27 Feb 2003 13:18:45 -0800
Message-Id: <5.2.0.9.2.20030227161431.05132898@shockey.us>
X-Sender: richard@shockey.us
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 27 Feb 2003 16:18:39 -0500
To: Pete Resnick <presnick@qualcomm.com>, karn@qualcomm.com
From: Richard Shockey <richard@shockey.us>
Subject: Re: IAB policy on anti-spam mechanisms?
Cc: ietf@ietf.org
In-Reply-To: <p06000808ba8413027bfa@[216.43.25.67]>
References: <E18oF2p-0001JN-00@maude.qualcomm.com>
 <E18oF2p-0001JN-00@maude.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf@ietf.org
Precedence: bulk

At 01:13 PM 2/27/2003 -0600, Pete Resnick wrote:
>On 2/26/03 at 7:49 PM -0800, Phil Karn wrote:
>
>>I would like to propose that the IAB consider drafting and adopting a 
>>position statement on the highly deleterious effect that certain 
>>anti-spam mechanisms have on legitimate, efficient uses of the Internet.
>
>It seems to me that this is a perfect topic to be discussed at the 
>Thursday morning Anti-Spam IRTF group meeting.


I agree ...but for those of you who live in the United States, The Federal 
Trade Commission is holding a 3 day workshop on combating spam.

http://www.ftc.gov/opa/2003/02/spamforum.htm

For those of you more politically inclined as well as technically 
knowledgeable about the subject I would encourage you to participate.

I have personally had some dealings with the FTC on privacy related issues 
as it relates to ENUM and in general I have found the Commission staff to 
be most grateful for knowledgeable, professional, technical opinions from 
folks like us.



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
Voice +1 571.434.5651 Cell : +1 314.503.0640,  Fax: +1 815.333.1237
<mailto:richard@shockey.us> or <mailto:richard.shockey@neustar.biz>
  <http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




From owner-ietf@ietf.org  Thu Feb 27 20:38:20 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29967;
	Thu, 27 Feb 2003 20:38:20 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oZL9-0004ZV-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 20:29:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oZKF-0004SY-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 20:28:35 -0500
Received: from slarti.muc.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29532
	for <ietf@ietf.org>; Thu, 27 Feb 2003 20:18:02 -0500 (EST)
Received: (qmail 25795 invoked by uid 66); 28 Feb 2003 01:21:58 -0000
Received: from faerber.muc.de by slarti.muc.de with BSMTP (rsmtp-qm-ot 0.4) for ietf@ietf.org; 28 Feb 2003 01:21:58 -0000
Received: by faerber.muc.de (OpenXP/32 v3.9.4 (Win32) alpha @ 2003-02-28-0038d);
	  28 Feb 2003 02:21:49 +0000
Date: 28 Feb 2003 00:00:00 +0000
From: claus@faerber.muc.de (=?ISO-8859-1?Q?Claus_F=E4rber?=)
To: ietf@ietf.org
Message-ID: <8giJ0Pz3cDD@3247.org>
In-Reply-To: <20030225005042.72047.qmail@cr.yp.to>
Subject: Re: Poison in a zone
User-Agent: OpenXP/32 v3.9.4 (Win32) alpha @ 2003-02-28-0038d
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

D. J. Bernstein <djb@cr.yp.to> schrieb/wrote:
> A moment ago we were being told how vitally important it was for AXFR
> clients to preserve all records received under all circumstances:
>    * ``An ACURATE [sic] copy of the zone is ESSENTIAL'';
>    * ``A modified zone is NOT a [sic] ACURATE [sic] copy. It's not
>      even a copy. It is a derived work'';

Well, djb raises an intersting question here: Is that really necessary?
Or, even one step further: Is it necessary that all authorative servers
have the same SOA record for a zone, especially the serial number?

I think the only requirement that's really essential is that the serial
number changes whenever the data that would be returned by a zone
transfer changes (even if that breaks database consistency for the SOA
record's serial number).

One strategy to implement this would be to keep an exact copy of a zone
obtained from other servers for outgoing transfers (so you'll always use
the original serial number), which is the BIND 9 strategy.

Another strategy would be to just increment the serial number of a zone
when it is actually changed by importing glue records from another zone.
This would solve the synchronisation problem, too: If the parent zone is
updated too early, the server might throw away the glue record. But it
will update the parent zone and increase its the serial number when it
gets an up-to-date copy of the child zone.

Claus
-- 
http://www.faerber.muc.de/



From owner-ietf@ietf.org  Thu Feb 27 20:38:28 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29992;
	Thu, 27 Feb 2003 20:38:27 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oZXj-00061R-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 20:42:31 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oZWm-0005uV-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 20:41:32 -0500
Received: from maude.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29703
	for <ietf@ietf.org>; Thu, 27 Feb 2003 20:30:58 -0500 (EST)
Received: from karn by maude.qualcomm.com with local (Exim 3.35 #1 (Debian))
	id 18oZQM-0001fp-00; Thu, 27 Feb 2003 17:34:54 -0800
From: ietf1@ka9q.net
To: jrace@attglobal.net
Cc: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
Reply-to: karn@qualcomm.com
Message-Id: <E18oZQM-0001fp-00@maude.qualcomm.com>
Date: Thu, 27 Feb 2003 17:34:54 -0800
Sender: owner-ietf@ietf.org
Precedence: bulk

>It seems there's a need to balance interests among different groups of
>users.   What is your proposed solution to prevent emission of
>spam via dialup, if you propose to discourage the DUL?  (My
>proposal imposes a positive duty of care of ISPs to prevent
>emission of spam, so I am quite concerned about this.)

Your question assumes that the DUL is actually a meaningful anti-spam
mechanism. It is not. So I should turn it around and ask you to state
exactly why you believe otherwise.

That said, I can say that it's no big deal for an ISP to determine
which of its customers had a given IP address at a certain time, as
this information is generally logged anyway. So allowing direct SMTP
in no way makes it harder to trace a spam complaint back to a user
account.

>Behavioral Studies 1 teaches that responsibility is ensured only
>by accountability, and accountability entails traceability.  What
>is your alternative to ensure traceability for abusive transmissions?

I have just stated it.

>Could you explain this please?   The difficulty I foresee is that
>ISPs are under legal obligations to prevent their property from being
>abused to injure others.  (Unfortunately many ISPs don't fulfill
>their obligation diligently as of now, but that is another story.)
>If the ISP chooses system-wide blocking, how could it be disabled
>on a per-user basis without facilitating spamming?

Certainly. Just about every ISP (except for those run as fronts by the
spammers themselves) has an acceptable use policy that prohibits
spamming along with activities that are actually illegal. Nearly every
ISP maintains an "abuse" address to which complaints can be sent. I
use these addresses myself on a regular basis, either directly or
through spamcop.

I see nothing wrong with holding users accountable after the fact for
spamming or illegal activities. My only problem is with pre-emptive
mechanisms that block perfectly legitimate applications and hurt
people who have never spammed or broken the rules.

It is as if George W had dropped a 10 megaton nuke on Baghdad, saying
that stopping Saddam was more important than avoiding "collateral
damage" to the civilian population. When you're so powerful that no
one is in a position to stop you, you can easily invent your own
justifications for anything you do.

>Well in fact collateral damage is the ONLY THING that motivates
>certain scum ISPs to reform, as has been repeatedly proven.  I can
>give you the cites if you like.   So collateral damage may have to
>be viewed as an interim necessity given the low ethical standards
>of some of the leading firms in the industry.

I have no problem with blacklists that contain IP addresses of hosts
actually known to generate or relay spam, as long as the owners of
those hosts are given the opportunity to fix the problem and be
removed from the blacklist. These are relatively narrow, focused and
effective mechanisms. Again, my only problem is with mechanisms that
are claimed to fight spam but in reality do little but hurt many
perfectly legitimate users.

Phil



From owner-ietf@ietf.org  Thu Feb 27 21:07:24 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00541;
	Thu, 27 Feb 2003 21:07:23 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oZzm-0001cu-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 21:11:30 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oZyg-0001QM-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 21:10:22 -0500
Received: from maude.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00376
	for <ietf@ietf.org>; Thu, 27 Feb 2003 20:59:49 -0500 (EST)
Received: from karn by maude.qualcomm.com with local (Exim 3.35 #1 (Debian))
	id 18oZsI-0001gM-00; Thu, 27 Feb 2003 18:03:46 -0800
From: ietf1@ka9q.net
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
Reply-to: karn@qualcomm.com
Message-Id: <E18oZsI-0001gM-00@maude.qualcomm.com>
Date: Thu, 27 Feb 2003 18:03:46 -0800
Sender: owner-ietf@ietf.org
Precedence: bulk

>Yup, the problem with well-known ports is that well-known port numbers
>get either (a) blocked by misguded ISP's, or (b) transparently proxed
>by misguided ISP's.  Since I have no idea what sort of stupidity I
>might encounter at various different hotel, conference, or 802.11
>hotspot networks, it's more convenient for me to use a non-standard
>port.

Another approach is to tunnel your SMTP connections over
SSH. So far most ISPs that block port 25 do seem to permit SSH.

I've been saying for some time that the single most important role for
encryption on the Internet may well be the defense of its end-to-end
model against encroachment by greedy, incompetent or misguided ISPs.

>The MUA issue isn't important in my case, because I run a local MTA on
>my latop (exim), which is configured to do the STARTTLS and AUTH, so I
>can use any MUA I wish.

Ah, but then you're running a *mail server*, which puts you in
violation of your local ISP's rules even if your MTA does not permit
relaying!

Believe it or not, I have actually been given this exact argument by
someone at MAPS whom I've been trying (unsuccessfully) to convince
that the MAPS DUL is a fundamantally flawed idea.

This is the mentality we're up against. I think a clear statement
by the IAB/IETF, even though it would not be binding in any legal sense,
would carry a lot of weight against this kind of braindamage.

Phil



From owner-ietf@ietf.org  Thu Feb 27 23:08:48 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02707;
	Thu, 27 Feb 2003 23:08:48 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18obrn-0004r8-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 23:11:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18obpZ-0004j7-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 23:09:05 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02436
	for <ietf@ietf.org>; Thu, 27 Feb 2003 22:58:30 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h1S42IU3016593
	for ietf@ietf.org env-from <vjs>;
	Thu, 27 Feb 2003 21:02:18 -0700 (MST)
Date: Thu, 27 Feb 2003 21:02:18 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200302280402.h1S42IU3016593@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
References: <E18oZsI-0001gM-00@maude.qualcomm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> Ah, but then you're running a *mail server*, which puts you in
> violation of your local ISP's rules even if your MTA does not permit
> relaying!
>
> Believe it or not, I have actually been given this exact argument by
> someone at MAPS whom I've been trying (unsuccessfully) to convince
> that the MAPS DUL is a fundamantally flawed idea.
>
> This is the mentality we're up against. I think a clear statement
> by the IAB/IETF, even though it would not be binding in any legal sense,
> would carry a lot of weight against this kind of braindamage.
>
> Phil

It's worthwhile to guess motives.  If you guess right, you can make
better predictions of others' actions and might find something
useful for your tactics.

As you've pointed out, the old claims from UUnet and others about the
difficulties in identifying individual spamming dialup users is knowingly
false.  They all do billing.  Contrary to many ISPs, it's also not as
if credit card numbers are useless for identifying people; if that were
true, then almost all commerce involving credit cards would be impossible.
...well, unless you believe that the only use of stolen or new credit
card numbers is for buying connect time to spam.

So why do ISPs lie and say they can't identify spammers?  Why do
they eagerly submit their own IP addresses to the DUL and the PDL**,
thereby inconveniencing many of their paying, non-spamming customers?
It's not as if there is no way to detect people using nailed-up modem
connections or that SMTP servers are the most expensive things a
customer can do with a nailed-up line.  I think the answer to both is
covered by
  - greed
     Passing TCP SYNs to port 25 allows the use of other ISPs mail
     systems.  Let the lusers off the reservation, and who knows what
     bad ideas they might get.  Perhaps worse, their mail might not
     include advertisements such as in mail from MSN and Hotmail users.

  - cheap and lazy
     checking logs for nailed up modems or actually reading and doing
     something with spam reports is far more expensive and requires more
     effort than filtering SYNs.  Charging or terminating resellers
     for their spammers risks alienating resellers.

  - pointed hair
     ...

The interesting question is whether a clear statement by the IETF
would help.  Because of the pointed hair, I think the answer is yes.


Vernon Schryver    vjs@rhyolite.com

**In case you missed the amazing soap opera episodes in which MAPS
sued the creator of MAP's DUL, see http://www.pan-am.ca/pdl/ and the
pages found by http://www.google.com/search?q=MAPS+lawsuit+dul



From owner-ietf@ietf.org  Thu Feb 27 23:45:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03300;
	Thu, 27 Feb 2003 23:45:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ocSl-0007s6-00
	for ietf-list@ran.ietf.org; Thu, 27 Feb 2003 23:49:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ocSV-0007oS-00
	for ietf@ran.ietf.org; Thu, 27 Feb 2003 23:49:19 -0500
Received: from mail.asianet.co.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03174
	for <ietf@ietf.org>; Thu, 27 Feb 2003 23:38:44 -0500 (EST)
Message-Id: <200302280438.XAA03174@ietf.org>
Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.198])
          (envelope-sender <jrace@attglobal.net>)
          by mail3.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 11:43:13 +0700
Received: from ppp-203.144.179.196.revip.asianet.co.th (HELO localhost) ([203.144.179.196])
          (envelope-sender <jrace@attglobal.net>)
          by mx1.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <jrace@attglobal.net>; 28 Feb 2003 11:42:34 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "Dr. Jeffrey Race" <jrace@attglobal.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 28 Feb 2003 11:42:27 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: IAB policy on anti-spam mechanisms?
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu, 27 Feb 2003 17:34:54 -0800, ietf1@ka9q.net wrote:

>Certainly. Just about every ISP (except for those run as fronts by the
>spammers themselves) has an acceptable use policy that prohibits
>spamming along with activities that are actually illegal. Nearly every
>ISP maintains an "abuse" address to which complaints can be sent. I
>use these addresses myself on a regular basis, either directly or
>through spamcop.
>
>I see nothing wrong with holding users accountable after the fact for
>spamming or illegal activities. My only problem is with pre-emptive
>mechanisms that block perfectly legitimate applications and hurt
>people who have never spammed or broken the rules.

The default is blocking Port 25.  Would an acceptable compromise
be to make IAB policy that Port 25 would be opened to legitimate
customers, just as rate-limited is relaxed now for legitimate
users upon application?   This would preserve the block against
Black Hats while allowing legit users like yourself to do your
business.  

Do any ISPs now have such a policy?

Jeffrey Race




From owner-ietf@ietf.org  Thu Feb 27 23:56:07 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03500;
	Thu, 27 Feb 2003 23:56:07 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ocfB-0000Yj-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 00:02:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oceZ-0000VA-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 00:01:47 -0500
Received: from mail.asianet.co.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03406
	for <ietf@ietf.org>; Thu, 27 Feb 2003 23:51:12 -0500 (EST)
Message-Id: <200302280451.XAA03406@ietf.org>
Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.197])
          (envelope-sender <jrace@attglobal.net>)
          by mail3.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 11:55:43 +0700
Received: from ppp-203.144.179.196.revip.asianet.co.th (HELO localhost) ([203.144.179.196])
          (envelope-sender <jrace@attglobal.net>)
          by mx1.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 11:55:04 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "Dr. Jeffrey Race" <jrace@attglobal.net>
Date: Fri, 28 Feb 2003 11:54:56 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: IAB policy on anti-spam mechanisms?
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Thu, 27 Feb 2003 10:48:31 -0700 (MST), Vernon Schryver wrote:

>UUNet in particular has demonstrated this sad syndrome.  For years,
>instead of ejecting its spamming and spam-friendly resellers, it lied.
>Then it lied for years about installing port 25 filtering.  Finally,
>it got port 25 filtering working, and reduced the amount of dial-up
>spam it was spewing.  All of that was instead of enforcing an anti-spam
>AUP and genuinely cracking down on spammers.  (By "lies" I mean official
>public statements in news.admin.net-abuse.email and to individuals that
>the UUnet spokesmen could not possibly have failed to know were false.)
>
>Of course, UUNet is far from the only example.  Another good one is
>Sprint, which had the audacity to claim to not know how to use ANI to
>find spammers running up 5-figure bills on stolen credit numbers or
>how to interest law enforcement agencies....this from a telco!

I have to second the comments about UUNet and Sprint from my own
personal experience.  I served up a complete case for prosecution
under the Va Computer Crimes Act, including the legal service address
and all logs.  The UUNet counsel (Neil Patel) refused to take any
action.   He told me this was management policy.  The fact is UUNet
profited from spamming.  We know from their subsequent collapse that
dishonesty pervaded the firm (maybe still does).

With another carrier, instead with good ethical standards (AT&T), an
incident I document (see <http://www.camblab.com/nugget/spam_03.pdf>) 
the problem was negligence, rather than witting enablement of
criminal activity.   (The frontline saps didn't even validate the
credit cards until the first billing period, so the users of stolen
cards had a whole month.   This went on for about 6 months until
I jerked management's chain; they stopped it as soon as they noticed
it.   But management were "too busy" with other things until someone
screamed.  I am an AT&T customer.  This is the Environmental Polluter
business model.)

I am about to nominate a solution for these problems.   Watch this
space.  (In the meantime read above PDF file.)

Jeffrey Race




From owner-ietf@ietf.org  Fri Feb 28 00:17:44 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03805;
	Fri, 28 Feb 2003 00:17:44 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ocwd-0001yu-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 00:20:27 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ocvW-0001rT-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 00:19:18 -0500
Received: from sleekfreak.ath.cx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03712
	for <ietf@ietf.org>; Fri, 28 Feb 2003 00:08:42 -0500 (EST)
Received: from localhost ([127.0.0.1] ident=shogunx)
	by sleekfreak.ath.cx with esmtp (Exim 3.35 #1 (Debian))
	id 18oQeZ-0001p4-00; Thu, 27 Feb 2003 11:12:59 -0500
Date: Thu, 27 Feb 2003 11:12:58 -0500 (EST)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: john smith <johnsmith0302@hotmail.com>
cc: ietf@ietf.org
Subject: Re: cables
In-Reply-To: <OE40nc09rVAV7BJPvy30000af06@hotmail.com>
Message-ID: <Pine.LNX.4.44.0302271108110.6990-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf@ietf.org
Precedence: bulk

On Fri, 28 Feb 2003, john smith wrote:

> "standard" time?
>
> rather than arguing about "standards" on ietf?
>
Perhaps.  It was a ring.  If you have constructed a bit of infrastructure
yourself, you will know the purpose of these.  It was made from commodity
hardware... what i had available at the time.  In fact, I was out of cat-5
when i closed the ring.  I seem to remember soldering a few wires to the
back of the network card:)  My concern is that this is the proper venue to
expound on the idea.  Perhaps the IEEE would be better suited in
addressing the change you propose.  It would indeed make grid networking
infinitely simpler, as well as changing the basic topology of the network
as a whole.  All in all not a bad idea.  By the way, who are you?  I don't
think I have had the pleasure of making your acquaintence...

Scott
>
> ----- Original Message -----
> From: shogunx <shogunx@sleekfreak.ath.cx>
> To: john smith <johnsmith0302@hotmail.com>
> Cc: <ietf@ietf.org>
> Sent: Thursday, February 27, 2003 9:43 AM
> Subject: Re: cables
>
>
> > On Thu, 20 Feb 2003, john smith wrote:
> >
> > >
> > > on ethernet,
> > >
> > >
> > > If all ports were DTE pin configured (same pair everywhere for rx and
> tx)
> > >
> > > and all cables were cross
> > >
> > > life would be simpler.
> >
> > I once built a network using nothing but cross-connects.  It was nice.
> >
> > Scott
> >
> > >
> > > -JS
> > >
> > >
> > >
> > >
> > >
> >
> > sleekfreak pirate broadcast
> > world tour 2002-3
> > live from daytona beach
> > http://sleekfreak.ath.cx
> >
> >
>

sleekfreak pirate broadcast
world tour 2002-3
live from daytona beach
http://sleekfreak.ath.cx




From owner-ietf@ietf.org  Fri Feb 28 01:52:00 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05349;
	Fri, 28 Feb 2003 01:52:00 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oeKk-0008GT-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 01:49:26 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oeKW-0008Cs-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 01:49:12 -0500
Received: from eikenes.alvestrand.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05185
	for <ietf@ietf.org>; Fri, 28 Feb 2003 01:38:36 -0500 (EST)
Received: from HALVESTR-W2K1.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6A71A6230A; Fri, 28 Feb 2003 07:42:30 +0100 (CET)
Date: Fri, 28 Feb 2003 14:33:43 +0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: grenville armitage <garmitage@swin.edu.au>, ietf@ietf.org
Subject: Re: Posting statistics for the IETF list
Message-ID: <57981793.1046442823@localhost>
In-Reply-To: <3E5DC89C.FBDC04CA@swin.edu.au>
References: <59138256.1046359676@localhost> <3E5DC89C.FBDC04CA@swin.edu.au>
X-Mailer: Mulberry/3.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 27. februar 2003 19:13 +1100 grenville armitage 
<garmitage@swin.edu.au> wrote:

>
> Harald Tveit Alvestrand wrote:
>>
>> Top posters to the IETF list, for the period of Jan 21 to Feb 26:
> 	[..]
>> No comment.
>
> Perhaps you should. Comment on whether this will become a regular
> thing, whether the 21st of one month to the 26th of the next will
> be a regular sample interval, or whether there was some other point
> you really wanted to make. There are a number of conclusions we could
> draw in the absence of proper guidance.

my impression is that mr. Bernstein has been making one single argument 23 
times, and that Dean Anderson has said that he supports Bernstein's 
argument 17 times, while Mark Andrews has said that he disagrees 19 times. 
At varying levels of detail.

While a rapid scan of the list of argumentative mails may give the 
impression that the volume of mail is 2-to-1 in favour of mr. Bernstein, I 
don't think we should attach more credibility to an argument (either pro or 
contra) because it is repeated many times.

That's what I think; others may feel differently... and no, I don't intend 
to do this often; it was just something I wondered about, and I had this 
script lying about.... the time interval is an artifact of the way I keep 
mail around....

                       Harald






From owner-ietf@ietf.org  Fri Feb 28 03:01:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16910;
	Fri, 28 Feb 2003 03:01:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ofYE-0004sa-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 03:07:26 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oEb0-0001Cr-00
	for ietf@ran.ietf.org; Wed, 26 Feb 2003 22:20:30 -0500
Received: from maggie.ka9q.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06847
	for <ietf@ietf.org>; Wed, 26 Feb 2003 22:10:07 -0500 (EST)
Received: from [127.0.0.1] (helo=qualcomm.com)
	by maggie.ka9q.net with esmtp (Exim 3.35 #1 (Debian))
	id 18oEUk-0000CS-00
	for <ietf@ietf.org>; Wed, 26 Feb 2003 19:14:02 -0800
Message-ID: <3E5D8279.2060802@qualcomm.com>
Date: Wed, 26 Feb 2003 19:14:01 -0800
From: Phil Karn <karn@qualcomm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IAB policy on anti-spam mechanisms?
X-Enigmail-Version: 0.73.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I would like to propose that the IAB consider drafting and adopting a 
position statement on the highly deleterious effect that certain 
anti-spam mechanisms have on legitimate, efficient uses of the Internet.

I am thinking mainly of the MAPS DUL (Dialup User List), a remarkably 
ill-conceived mechanism that complicates life considerably for those who 
prefer not to use their ISP's mail servers for reasons of efficiency, 
latency and security while doing remarkably little (or nothing) to 
actually combat spam.

Here's a page that says better than I can why MAPS DUL is such a bad idea:

http://homepages.tesco.net/~J.deBoynePollard/FGA/maps-dul-is-wrong.html

Other widely deployed but similarly misguided anti-spam mechanisms 
include blanket blocks on incoming or outgoing TCP connections to port 
25. I've even encountered on ISP that transparently and silently 
redirected my outbound SMTP connections to their own mail servers!

All these mechanisms force users to relay outbound or inbound mail 
through ISP-run mail servers. This increases latency, decreases 
reliability (sometimes substantially), and totally precludes the 
effective use of some very useful SMTP security features such as the 
AUTH and STARTTLS commands.

There is precedent for the IAB taking a stand on this sort of thing. In 
particular, RFC2775 on "Internet Transparency" expresses the view that 
the end-to-end principle that underlies the Internet architecture is 
still vitally important and worth preserving. Although RFC2775 spoke 
mainly to the problems introduced by the widespread use of NATs, spam 
filtering is mentioned in passing.

Another relevant precedent is RFC2804, "IETF Policy on Wiretapping", in 
which the IETF formally rejected calls to design Internet protocols to 
facilitate wiretapping. Yet anti-spam mechanisms that block direct 
end-to-end SMTP transfers effectively disables the routine use of 
STARTTLS, an automatic, transparent and highly effective 
anti-wiretapping mechanism, and makes it a trivial matter for an ISP to 
log every email sent or received by its users. At a time of 
unprecedented threats to personal privacy and security, the widespread 
use of mechanisms like STARTTLS should be encouraged, not discouraged.

As everyone knows, there are many different ideas and approaches to the 
spam problem, yet none of them has proven to be a silver bullet. There 
is plenty of room for innovation and experimention in this area, and I 
certainly wouldn't want to dampen these activities.

However, I believe the IETF and IAB should state some basic principles 
that should be observed by everyone working on the spam problem. And the 
most basic principle of all should be that no anti-spam mechanism should 
ever block email between consenting end-parties without giving those 
parties the ability to disable those blocking mechanisms.

As currently implemented, however, end users rarely (if ever) have such 
control. They are the "collateral damage" of the spam war, and are 
shrugged off just like foreign civilian casualties in most wars. But a 
formal policy statement by the IAB or IETF just might give them 
something to defend themselves.

Comments?

Phil






From owner-ietf@ietf.org  Fri Feb 28 03:01:54 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16909;
	Fri, 28 Feb 2003 03:01:54 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ofUL-0004eA-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 03:03:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18nAk5-0002JC-00
	for ietf@ran.ietf.org; Mon, 24 Feb 2003 00:01:29 -0500
Received: from mx4.tellabs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21164;
	Sun, 23 Feb 2003 23:51:54 -0500 (EST)
Received: from mailw02.hq.tellabs.com (mailw02.lisle.tellabs.com [172.23.207.12])
	by mx4.tellabs.com (Mirapoint Messaging Server MOS 3.3.2-CR)
	with ESMTP id ACH43180;
	Sun, 23 Feb 2003 22:55:45 -0600 (CST)
Received: from tellabs.com ([192.168.225.34]) by mailw02.hq.tellabs.com with ESMTP (8.9.3 (PHNE_24419)/8.7.1) id WAA05892; Sun, 23 Feb 2003 22:55:46 -0600 (CST)
Message-ID: <3E59A5B4.880B91D2@tellabs.com>
Date: Sun, 23 Feb 2003 22:55:16 -0600
From: Jonathan Sadler <jonathan.sadler@tellabs.com>
Reply-To: jonathan.sadler@tellabs.com
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: iesg@ietf.org, ietf@ietf.org, ccamp@ops.ietf.org
Subject: Re: Last Call: Routing Extensions in Support of Generalized MPLS  vto 
 Proposed Standard
References: <H0000c08064ac643.1044985131.mailw02@MHS>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mirapoint-Sig: mx4.tellabs.com
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Please consider the following comments on these drafts:
    draft-ietf-ccamp-gmpls-routing-05.txt
    draft-ietf-ccamp-ospf-gmpls-extensions-09.txt
Many of the comments are based on implementation experience.  These comments are
marked with a (*).

Jonathan Sadler

==========

1. In section 4.4.2 of draft-ietf-ccamp-gmpls-routing-05.txt, the operations for
Packet Switch Capable (PSC) are defined.  Reference is made to Minimum LSP bandwidth
for SDH encoding.  None of the examples in section 5 of
draft-ietf-ccamp-gmpls-routing-05.txt show how this field should filled.

2. The mechanism for showing relationships between server and client layers is not
generalized*.  Specifically:
  - Relationships between SONET/SDH layers (ISC type: TDM) are
    implicitly stated based on the Min and Max LSP bandwidth
    advertised*.  To quote draft-ietf-ccamp-gmpls-routing-05.txt:

     "On an interface having Standard SDH multiplexing, an LSP
      at priority p could reserve any bandwidth allowed by the
      branch of the SDH hierarchy, with the leaf and the root
      of the branch being defined by the Minimum LSP Bandwidth
      and the Maximum LSP Bandwidth at priority p."

    This requires node doing the route calculation to understand
    the G.707 multiplexing hierarchy.  Since LSP routing is source
    routed, it could be the node doing the route calculation
    doesn't understand G.707.

    Furthermore, the G.707 multiplexing hierarchy is not a simple
    tree.  For example VC-11 and VC-12 can be supported over VC-3
    as well as over VC-4.  Consequently, the definition provided
    does not allow a system to explicitly state which "branch" of
    the G.707 hierarchy should be followed.

  - Relationships between PSC-n (for IP switching) and SONET/SDH are
    explicitly specified on the encoding type specified in the PSC-n
    announcement*.  However, SONET/SDH is not a single layer.  It
    must be possible to identify if the PSC-n layer can be carried
    by a VC-11 trail, a VC-12 trail, a VC-3 trail, a VC-4 trail,
    or a VC-4-nc trail.

    Section 4.4.2 of draft-ietf-ccamp-gmpls-routing-05.txt tries
    to deal with this in the following paragraph:

     "On a PSC interface that supports Standard SDH encoding, an
      LSP at priority p could reserve any bandwidth allowed by
      the branch of the SDH hierarchy, with the leaf and the root
      of the branch being defined by the Minimum LSP Bandwidth
      and the Maximum LSP Bandwidth at priority p."

    The problem is this contradicts the following paragraph:

     "The Maximum LSP Bandwidth takes the place of the Maximum
      Bandwidth ([ISIS-TE], [OSPF-TE]). However, while Maximum
      Bandwidth is a single fixed value (usually simply the link
      capacity), Maximum LSP Bandwidth is carried per priority,
      and may vary as LSPs are set up and torn down."
    Specifically, how does a completely available OC-48 interface
    with VC-11 over VC-3, VC-3, and VC-4 get encoded?  Based on
    the first paragraph, the encoding would be MinLSPBW=1.5M, and
    MaxLSPBW[p]=155M.  Ignoring the issue that VC-11 over VC-4
    ends up being shown as supported, the second paragraph states
    that the MaxLSPBW[p] should be 2.5G.

    Knowing the OC-48 is completely available is useful information,
    as multiple VC-4s could be used in an LCAS group to support
    connections that need data rates over 155M*.

 - The mechanism does not support describing common muli-layer
   relationships such as IP over DS1 over VC-11 or IP over DS3
   over VC-3*.

 - Sometimes layer relationships are described in an "inverted"
   manner*. Section 5.1 of draft-ietf-ccamp-gmpls-routing-05.txt
   states:
     "STM-16 POS Interface on a LSR

          Interface Switching Capability Descriptor:
             Interface Switching Capability = PSC-1
             Encoding = SDH
             Max LSP Bandwidth[p] = 2.5 Gbps, for all p"

   Where PSC-1 is the client of an SDH (sic) server.

   Section 5.5 states:
      "Interface of an opaque OXC (SDH framed) with support for
       one lambda per port/interface"

      "   Interface Switching Capability Descriptor:
             Interface Switching Capability = LSC
             Encoding = SDH"

   In this case, SDH is a client of a wavelength server (LSC).
   However, unlike in section 5.1, the layer relationship is
   inverted.

3. Layer specific attributes are not supported*.  Specifically:
 - It is not possible to have a link with different costs at
   different layers (ex. VC-11, VC-4, VC4-4c).  The link cost
   is a tool used by network designers to bias traffic toward or
   away from specific links.

   Since different hardware platforms are optimized for different
   layers, the network designer may wish to bias traffic in a layer
   to use or avoid a platform that inefficiently supports a
   particular layer.  The announcement of a link in the layer may
   still be desirable to allow for diverse routing.

 - Many attributes discussed actually refer to a specific layer*.
   For example SRLG can be an MS-layer attribute that is inherited
   by all supported layers (VC-11, VC-12, VC-3, VC-4, VC-4-nc).
   Likewise Protection mechanisms supported can be specified at
   the MS-layer and the path layer.

   Knowing the specific layer the attributes exist at allow for
   higher quality routes to be developed*.  It can also allow for
   proper provisioning of upper layer functions, such as protection
   hold off timers*.

 - Combining layer specific attributes with layer relationships can
   provide a more efficient encoding mechanism than requiring
   separate link announcements per layer*.

4. The "TDM" Interface Switching Capability presumably includes
   layers other than SONET/SDH, such as PDH* (DS1, DS3, E1, E3) and
   G.709.  The interaction with these layers needs to be defined.

5. In many cases, 8 levels of priority are not necessary*.  A more
   compact encoding that has a bitfield stating the priority levels
   being announced would reduce the size of the announcement.

The IESG wrote:

> The IESG has received a request from the Common Control and Measurement
> Plane Working Group to consider publication of the following two
> Internet-Drafts as Proposed Standards:
>
> o Routing Extensions in Support of Generalized MPLS
>     <draft-ietf-ccamp-gmpls-routing-05.txt>
> o OSPF Extensions in Support of Generalized MPLS
>     <draft-ietf-ccamp-ospf-gmpls-extensions-09.txt>
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-2-24.
>
> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-routing-05.txt
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-ospf-gmpls-extensions-09.txt

============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================





From owner-ietf@ietf.org  Fri Feb 28 03:39:43 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17427;
	Fri, 28 Feb 2003 03:39:43 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18og83-0007lT-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 03:44:27 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18og7H-0007ht-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 03:43:39 -0500
Received: from mail.asianet.co.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17336
	for <ietf@ietf.org>; Fri, 28 Feb 2003 03:33:03 -0500 (EST)
Message-Id: <200302280833.DAA17336@ietf.org>
Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.198])
          (envelope-sender <jrace@attglobal.net>)
          by mail2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 15:36:56 +0700
Received: from ppp-203.144.202.213.revip.asianet.co.th (HELO localhost) ([203.144.202.213])
          (envelope-sender <jrace@attglobal.net>)
          by mx2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 15:27:35 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "Dr. Jeffrey Race" <jrace@attglobal.net>
Date: Fri, 28 Feb 2003 15:36:47 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: IAB policy on anti-spam mechanisms?
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Wed, 26 Feb 2003 19:49:15 -0800, ietf1@ka9q.net wrote:
[snip]
>
>There is precedent for the IAB taking a stand on this sort of
>thing. In particular, RFC2775 on "Internet Transparency" expresses the
>view that the end-to-end principle that underlies the Internet
>architecture is still vitally important and worth preserving. Although
>RFC2775 spoke mainly to the problems introduced by the widespread use
>of NATs, spam filtering is mentioned in passing.
>

Thanks for the reference to RFC2775 which I have now read.  I
understand it to say end-to-end transparency with unique addresses
was the guiding principle in the days of essentially limitless IP
addresses and an environment of trust.   It then seems to go on to
say that there are now valid reasons (having to do with shortage
of IP addresses under IPv4 and with insecurity from the rabble now
infesting the Net) which have produced an acceptable limitation on
the earlier guiding principle. 

I may read this wrongly and welcome correction.

Jeffrey Race




From owner-ietf@ietf.org  Fri Feb 28 04:51:32 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18842;
	Fri, 28 Feb 2003 04:51:32 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ohCn-0003zl-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 04:53:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ohCB-0003wO-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 04:52:47 -0500
Received: from laposte.rennes.enst-bretagne.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18681
	for <ietf@ietf.org>; Fri, 28 Feb 2003 04:42:09 -0500 (EST)
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id h1S9k3h01326;
	Fri, 28 Feb 2003 10:46:03 +0100
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id h1S9gaof071616;
	Fri, 28 Feb 2003 10:42:36 +0100 (CET)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200302280942.h1S9gaof071616@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
cc: IETF <ietf@ietf.org>
Subject: Re: IAB policy on anti-spam mechanisms? 
In-reply-to: Your message of Thu, 27 Feb 2003 14:33:48 EST.
             <200302271933.h1RJXnNw025959@marajade.sandelman.ottawa.on.ca> 
Date: Fri, 28 Feb 2003 10:42:36 +0100
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Sender: owner-ietf@ietf.org
Precedence: bulk

 In your previous mail you wrote:

   The "nicest" solution that I can see is for the ISPs to transparently
   proxy port 25 to their MTA. They should offer STARTTLS.
   
=> I don't understand the word "transparently" here (:-). If one of
my ISPs does such things, I'll sue it immediately: we have laws in
France to protect the secrecy of private mails. I'll be surprised
if there is none in USA.

   So, my packets look like:
       SMTP/TLS/TCP/IPv6/IPv4-encap-v6/IPsec/IPv4.
   
=> yes, the protocol 50 will save us from them (I'll put this on a T-shirt :-).

Thanks

Francis.Dupont@enst-bretagne.fr



From owner-ietf@ietf.org  Fri Feb 28 05:21:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19405;
	Fri, 28 Feb 2003 05:21:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ohkM-0006Vb-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 05:28:06 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ohj1-0006S6-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 05:26:43 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA19332
	for <ietf@ietf.org>; Fri, 28 Feb 2003 05:16:06 -0500 (EST)
Received: (qmail 14085 invoked by uid 1017); 28 Feb 2003 10:20:29 -0000
Date: 28 Feb 2003 10:20:29 -0000
Message-ID: <20030228102029.14084.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: ietf@ietf.org
Subject: Re: Posting statistics for the IETF list
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Alvestrand writes:
> I don't think we should attach more credibility to an argument
> (either pro or contra) because it is repeated many times.

If you were paying attention instead of mindlessly counting From lines,
you'd see that the discussion has covered many different issues, and
that various errors have been much more clearly exposed than they were
at the beginning. For example, the BIND company has admitted that the
``zone coherency'' rule is violated by BIND 9.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 28 07:31:02 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23203;
	Fri, 28 Feb 2003 07:31:02 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ojhd-00088t-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 07:33:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ojhG-00085R-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 07:33:02 -0500
Received: from mail-blue.research.att.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22148
	for <ietf@ietf.org>; Fri, 28 Feb 2003 07:22:23 -0500 (EST)
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 664804CE6A; Fri, 28 Feb 2003 07:26:20 -0500 (EST)
Received: from berkshire.research.att.com (raptor.research.att.com [135.207.23.32])
	by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id h1SCQJB25480;
	Fri, 28 Feb 2003 07:26:20 -0500 (EST)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 53CCF7B4D; Fri, 28 Feb 2003 07:26:19 -0500 (EST)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: ietf@ietf.org
Subject: Re: Posting statistics for the IETF list 
In-Reply-To: Your message of "28 Feb 2003 10:20:29 GMT."
             <20030228102029.14084.qmail@cr.yp.to> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 28 Feb 2003 07:26:19 -0500
Message-Id: <20030228122619.53CCF7B4D@berkshire.research.att.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

>  For example, the BIND company has admitted that the
>``zone coherency'' rule is violated by BIND 9.


Dan, 1034 itself says that absolute consistency is a non-goal.  From 2.3:

     Access to information is more critical than instantaneous
     updates or guarantees of consistency.  Hence the update
     process allows updates to percolate out through the users of
     the domain system rather than guaranteeing that all copies are
     simultaneously updated.




		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)





From owner-ietf@ietf.org  Fri Feb 28 09:47:11 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00227;
	Fri, 28 Feb 2003 09:47:11 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18olo1-0005ev-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 09:48:09 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18olmS-0005VJ-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 09:46:32 -0500
Received: from htt-consult.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29815
	for <ietf@ietf.org>; Fri, 28 Feb 2003 09:35:50 -0500 (EST)
Received: from port3490.htt-consult.com ([65.84.78.209]) by htt-consult.com ; Fri, 28 Feb 2003 09:37:38 -0500
Message-Id: <5.1.0.14.2.20030228093138.03082640@localhost>
X-Sender: rgm-ietf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 28 Feb 2003 09:32:42 -0500
To: "Dr. Jeffrey Race" <jrace@attglobal.net>, "ietf@ietf.org" <ietf@ietf.org>,
        "karn@qualcomm.com" <karn@qualcomm.com>
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Subject: Re: IAB policy on anti-spam mechanisms?
In-Reply-To: <200302271518.KAA07652@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Rcpt-To: <karn@qualcomm.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

At 10:22 PM 2/27/2003 +0700, Dr. Jeffrey Race wrote:

>It seems there's a need to balance interests among different groups of
>users.   What is your proposed solution to prevent emission of
>spam via dialup, if you propose to discourage the DUL?  (My
>proposal imposes a positive duty of care of ISPs to prevent
>emission of spam, so I am quite concerned about this.)

Perhaps this is a business model for someone here?

For a modest fee to run an SSH gateway to allow tunneling past ISP policies  :)






From owner-ietf@ietf.org  Fri Feb 28 09:47:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00252;
	Fri, 28 Feb 2003 09:47:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18olnp-0005cO-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 09:47:57 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18olkM-0002z0-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 09:44:22 -0500
Received: from htt-consult.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29778
	for <ietf@ietf.org>; Fri, 28 Feb 2003 09:33:40 -0500 (EST)
Received: from port3490.htt-consult.com ([65.84.78.209]) by htt-consult.com ; Fri, 28 Feb 2003 09:37:37 -0500
Message-Id: <5.1.0.14.2.20030228092714.0309a458@localhost>
X-Sender: rgm-ietf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 28 Feb 2003 09:29:22 -0500
To: "Theodore Ts'o" <tytso@mit.edu>, karn@qualcomm.com
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Subject: Re: IAB policy on anti-spam mechanisms?
Cc: ietf@ietf.org
In-Reply-To: <20030227055538.GH24322@think.thunk.org>
References: <E18oF2p-0001JN-00@maude.qualcomm.com>
 <E18oF2p-0001JN-00@maude.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Rcpt-To: <ietf@ietf.org>
Sender: owner-ietf@ietf.org
Precedence: bulk

At 12:55 AM 2/27/2003 -0500, Theodore Ts'o wrote:

>Yup, some 802.11 wireless "hotspot" networks block port 25 as well.
>Very annoying.  My personal workaround to this is to have a personal
>server tucked away at a colo facility, which among other things, runs
>a SMTP server listening on port 2025 (to get around the port 25
>blocking insanity).  This SMTP server will relay e-mail on my behalf,
>no matter when I am in the Internet, after my laptop uses STARTTLS and
>AUTH to authenticate myself to my SMTP server.

May I add running this through SSH?  That is what I do.  All my outgoing 
SMTP and incoming POP is through SSH to my home server, protecting me from 
such nefarious operations.

I even found one 802.11 hotspot (WISPer), that did not have the SSH port 
blocked and I could have done all my work without paying (did anyway, as I 
want to encourage hotspot deployments).






From owner-ietf@ietf.org  Fri Feb 28 09:47:15 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00265;
	Fri, 28 Feb 2003 09:47:15 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oltH-0006GO-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 09:53:35 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oloN-0005lC-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 09:48:31 -0500
Received: from mail.asianet.co.th (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29831
	for <ietf@ietf.org>; Fri, 28 Feb 2003 09:37:49 -0500 (EST)
Message-Id: <200302281437.JAA29831@ietf.org>
Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.197])
          (envelope-sender <jrace@attglobal.net>)
          by mail3.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 21:42:21 +0700
Received: from ppp-203.144.202.213.revip.asianet.co.th (HELO localhost) ([203.144.202.213])
          (envelope-sender <jrace@attglobal.net>)
          by mx2.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <ietf@ietf.org>; 28 Feb 2003 21:32:24 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "ietf@ietf.org" <ietf@ietf.org>, "karn@qualcomm.com" <karn@qualcomm.com>,
        "Robert Moskowitz" <rgm-ietf@htt-consult.com>
Date: Fri, 28 Feb 2003 21:41:35 +0700
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: IAB policy on anti-spam mechanisms?
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Fri, 28 Feb 2003 09:32:42 -0500, Robert Moskowitz wrote:

>Perhaps this is a business model for someone here?
>
>For a modest fee to run an SSH gateway to allow tunneling past ISP 
policies  :)


I have collected a whole potful of constructive suggestions and
workarounds from my friends on Spam-L and will repost here (sans
attribution) shortly.

Jeffrey Race




From owner-ietf@ietf.org  Fri Feb 28 11:11:36 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03030;
	Fri, 28 Feb 2003 11:11:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18onAW-0000ds-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 11:15:28 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18on9i-0000Y3-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 11:14:38 -0500
Received: from above.proper.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02771
	for <ietf@ietf.org>; Fri, 28 Feb 2003 11:03:57 -0500 (EST)
Received: from [63.202.92.157] (adsl-63-202-92-157.dsl.snfc21.pacbell.net [63.202.92.157])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id h1SG7iY21797;
	Fri, 28 Feb 2003 08:07:44 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05210516ba8538cb6901@[63.202.92.157]>
In-Reply-To: <E18oZQM-0001fp-00@maude.qualcomm.com>
References: <E18oZQM-0001fp-00@maude.qualcomm.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report>.
Date: Fri, 28 Feb 2003 08:06:42 -0800
To: karn@qualcomm.com
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: IAB policy on anti-spam mechanisms?
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf@ietf.org
Precedence: bulk

At 5:34 PM -0800 2/27/03, ietf1@ka9q.net wrote:
>Your question assumes that the DUL is actually a meaningful anti-spam
>mechanism. It is not.

Could you elaborate a bit on what you mean by "meaningful"? As 
someone who uses the DUL list as an anti-spam mechanism and who 
experiments with turning it off and on, I can definitely say that 
turning it on reduces the amount of spam I receive (on the order of 
about 100 messages a day).

I recognize that it also harms folks like you for many of the reasons 
you give. But I don't understand why you say it is not a meaningful 
anti-spam mechanism.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf@ietf.org  Fri Feb 28 11:11:37 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03031;
	Fri, 28 Feb 2003 11:11:36 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18on8b-0000SH-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 11:13:29 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18on7k-0000MR-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 11:12:36 -0500
Received: from mail.speakeasy.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02750
	for <ietf@ietf.org>; Fri, 28 Feb 2003 11:01:55 -0500 (EST)
Received: (qmail 4234 invoked from network); 28 Feb 2003 16:05:54 -0000
Received: from unknown (HELO listen.to) (davearonson@[66.92.168.196])
          (envelope-sender <davearonson@listen.to>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with RC4-MD5 encrypted SMTP
          for <karn@qualcomm.com>; 28 Feb 2003 16:05:54 -0000
Message-ID: <3E5F7B51.9070208@hotpop.com>
Date: Fri, 28 Feb 2003 10:08:01 -0500
From: "David J. Aronson" <dja2003@hotpop.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: karn@qualcomm.com
CC: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
References: <E18oZQM-0001fp-00@maude.qualcomm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

ietf1@ka9q.net wrote:

> Just about every ISP (except for those run as fronts by the  spammers
> themselves) has an acceptable use policy that prohibits spamming

Many of the ones that are, or at least seem to be, run by the spammers, 
also have such AUPs.  They just enforce them even less than ScrewYouNet 
used to do!

(In all fairness, though, I must rise to the defense of UUNet's Security 
department.  Their abuse-address-of-the-month certainly was lax at 
nailing spammers.  However, if a spam was fresh enough out of UUNet's 
own gates that the spammer may well still be on line, I called the 
Security department.  They were usually quite happy to look at what was 
going across the line, and yank it if the client was spamming.  Or at 
least they SAID that's what they were doing....)

-- 
David J. Aronson, Software Engineer for hire in Washington DC area.
See http://destined.to/program/ for online resume, references, etc.





From owner-ietf@ietf.org  Fri Feb 28 14:49:39 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10478;
	Fri, 28 Feb 2003 14:49:39 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oqXS-0007YZ-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 14:51:22 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oqXL-0007We-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 14:51:15 -0500
Received: from zoe.office.snowshore.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10194;
	Fri, 28 Feb 2003 14:40:30 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [UM] RE: WG Review: Enhancements to Internet email to  support  diverse service environments (lemonade)
Date: Fri, 28 Feb 2003 14:46:38 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D248838@zoe.office.snowshore.com>
Thread-Topic: [UM] RE: WG Review: Enhancements to Internet email to  support  diverse service environments (lemonade)
Thread-Index: AcLdEA7EqEx/inPFQ6aHG0i8FTXPdQB8G1/Q
From: "Eric Burger" <eburger@snowshore.com>
To: "Dave Crocker" <dcrocker@brandenburg.com>
Cc: <ietf@ietf.org>, <iesg@ietf.org>,
        "IETF LEMONADE (E-mail)" <um@snowshore.com>
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA10478

It is unquestionably true that the motivation for the work group is to enable "lesser" access methods to work with Internet e-mail.  One may reasonably argue that optimization for a particular access method is not the work of the IETF.  That is, we usually say, "Fix the lesser access method."

However, I would offer two reasons to go ahead with the work.  The first is volume.  If one believes the projections for wireless data access, very shortly there will be orders of magnitude more "lesser"-connected devices than traditional Internet devices.  Said differently, it will be the traditional devices that will be in the minority.  By sheer economics, this may result in the marginalization of IETF protocols in favor of the more ubiquitous (and closed-process developed), explicitly-wireless protocols.

The second reason is that almost all of the extensions and adaptations proposed in the charter improves Internet mail in general.  Here are some examples.

 o  Remote submission: In the wireless environment, nobody wants to download a 40KB message to forward it.  Likewise, when I'm dialed up on my conventional PC, I don't want to download a 1MB message to forward it, either.

 o  Streaming: In the wireless environment, the latency associated with fully downloading a voice message before playing it is unacceptable.  In the conventional environment, the latency and storage associated with fully downloading a video object is unacceptable, too.

 o  Multimodal access: In the wireless environment, we get a small GUI and a TUI.  In the conventional environment, we will shortly be seeing integrated GUI, SUI (Speech User Interface), and Ink (Stylus User Interface) clients.


Dave hits upon an important point.  The goal of the work group is not to create a set of protocol extensions for some odd combination of proprietary and "walled garden" devices and networks.  The goal is to improve the Internet e-mail infrastructure in general, with the immediate goal in incorporating devices and networks of lesser capability.  We have an example of such an activity in the U.S.  The ADA law had the (intended) consequence of making access easier for EVERYONE, as well as those that are disabled.  In the same manner, the idea of lemonade is to improve e-mail for everyone.

Logical conclusion of this concept is that lemonade must not break e-mail for anyone.  Examples of what we don't want to do are creating a non-interoperable profile of SMTP or increasing the complexity of IMAP.

> -----Original Message-----
> From: Dave Crocker [mailto:dcrocker@brandenburg.com]
> Sent: Tuesday, February 25, 2003 3:52 PM
> To: Ted Hardie
> Cc: Eric Burger; John C Klensin; ned.freed@mrochek.com; Pete Resnick;
> ietf@ietf.org; iesg@ietf.org; UM list
> Subject: Re: [UM] RE: WG Review: Enhancements to Internet email to
> support diverse service environments (lemonade)
> 
> 
> Folks,
> 
> First of all, I must apologize. Sure enough, I was looking at an older
> version of the charter, in spite of having tried to avoid that error.
> The versions that I had seen listed a couple of specifics, in the task
> list portion, but it was only partial and the overall 
> document seemed to
> me to leave blind cliffs over which a WG could easily drive.
> 
> The current version lists specific actions that are clear and concise,
> except perhaps the one about gatewaying to other services 
> (more on that
> inline)
> 
> I gather that the IAB is frankly dictating the current wording of the
> opening paragraph. I am seriously dismayed to hear that. From 
> an offline
> exchange, Ned mentions a desire to have the paragraph include 
> something
> like "link characteristics of concern are those of high 
> latency and low
> bandwidth, the device characteristics are limited memory and 
> processing
> power, and the service environments are environments are MMS/WAP." I
> very heartily concur. In fact it is exactly what I think is missing.
> 
> Keeping the IAB happy is always important, but I do not believe it
> should result in a working group charter -- and especially not an
> opening paragraph -- that is more obscure. However the fact that the
> remainder of the charter is so specific moves my concern from 
> immediate
> and strong, to relatively theoretical.
> 
> Still if there is a way to enhance the opening paragraph, it really
> would be nice. Something like:
> 
>       Internet mail devices often operate with limited memory or
>       processing power, or with links that have high latency 
> and/or low
>       bandwidth. Existing Internet mail protocols are inefficient in
>       such environments. The Lemonade working group is tasked 
> to provide
>       a set of email enhancements that permit efficient operation in
>       resource-constrained computing and communication 
> environments. The
>       resulting specification(s) will be a seamless enhancement to
>       existing Internet mail.
> 
> I have not said anything about MMS/WAP because I have no idea what
> specifics are intended for dealing with them, in spite of 
> your comments.
> (Hence, for this issue, we are back to my original concern.)   More on
> that, below.
> 
> 
> Tuesday, February 25, 2003, 11:37:10 AM, you wrote:
> TH> problem here is that there are a set of services which are being
> TH> contemplated or deployed in specific environments which 
> are based on
> TH> IETF protocols but do not interoperate with them, either 
> well or at all.
> 
> and i certainly agree that we should find a way to avoid that outcome.
> 
> 
> TH> The list you saw above:  link characteristics, device 
> characteristics,
> TH> or service environments are the differences cited by 
> those operating
> TH> those service environments as reasons for wanting "profiles" of
> TH> IETF protocols that meet their needs.
> 
> and I certainly agree that the current protocols work badly 
> in a number
> of environments.
> 
> Hence, unsolicited new mail notification and re-use of server-based
> content will be spiffy enhancements.
> 
> I suspect the changes to support streaming content enhancement are
> really something more general, and will "simply" do a graceful job of
> moving the specifics of content handling to non-email subsystems,
> tailored for the particular content. At any rate, yes of course that
> will be a good enhancement too.
> 
> 
> >>      "A primary goal of this work is to ensure that those 
> profiles and
> >>      enhancements continue to interoperate with the 
> existing Internet
> >>      email protocols in use on the Internet, so that these 
> environments
> >>      and more traditional Internet users have access to a seamless
> >>      service."
> >>
> >>No doubt I am misinterpreting this, but it sure sounds as 
> if the goal is
> >>to create some sort of new email service and try to make 
> sure it can be
> >>gatewayed to existing Internet email services?
> 
> TH> Actually, avoiding the need to gateway between services is one of
> TH> my own goals for this work.
> 
> I used the term "gateway" very carefully.  It is exactly what 
> I get from
> the current wording.
> 
> My world model of interconnection is very simple: either the 
> upper-level
> service is end-to-end and homogeneous, or the interface is between
> independent, heterogeneous services. Multi-hop handling for the former
> is relaying; for the latter is is gatewaying (ie, translating). Moving
> the same content over different *underlying* environments is relaying.
> 
> From the current charter, I have no idea what is really intended,
> concerning MMS/WAP, except that the style of the current language sure
> makes me lean towards expecting gatewaying. (I'm delighted 
> that you have
> the intent of avoiding gatewaying, but now perhaps you can 
> appreciate my
> confusion.)
> 
> Perhaps the way to clarify this is to focus on what will be 
> true of the
> end participants, rather than what will not be true at the interface
> between two parts of the service?  Hence, mentioning the interface
> service because a derivative rather than a focus.
> 
> (Glad to thrash this privately with you, in an effort to come up with
> alternate language. Again, I can't offer any yet, because I can't tell
> what the specific issues and goals are.)
> 
> All of the above acknowledges that Time Is Passing(c).  Still, I've
> become totally paranoid about charters that are vague.
> 
> d/
> -- 
>  Dave <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  t +1.408.246.8253; f +1.408.850.1850
> 
> 



From owner-ietf@ietf.org  Fri Feb 28 19:15:17 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17843;
	Fri, 28 Feb 2003 19:15:17 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oudz-0007RO-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 19:14:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oud6-0007QP-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 19:13:28 -0500
Received: from gusto.araneus.fi (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17574
	for <ietf@ietf.org>; Fri, 28 Feb 2003 19:04:39 -0500 (EST)
Received: from guava.araneus.fi (adsl-63-197-0-204.dsl.snfc21.pacbell.net [63.197.0.204])
	by gusto.araneus.fi (8.11.6/8.11.6) with ESMTP id h2106aB14149;
	Fri, 28 Feb 2003 16:06:36 -0800 (PST)
Received: (from gson@localhost)
	by guava.araneus.fi (8.11.6/8.11.6) id h2106Zm21440;
	Fri, 28 Feb 2003 16:06:35 -0800 (PST)
Date: Fri, 28 Feb 2003 16:06:35 -0800 (PST)
Message-Id: <200303010006.h2106Zm21440@guava.araneus.fi>
To: claus@faerber.muc.de (=?ISO-8859-1?Q?Claus_F=E4rber?=)
CC: namedroppers@ops.ietf.org
Cc: ietf@ietf.org
Subject: Re: Poison in a zone
In-Reply-To: <8giJ0Pz3cDD@3247.org>
References: <20030225005042.72047.qmail@cr.yp.to>
	<8giJ0Pz3cDD@3247.org>
X-Mailer: VM 7.04 under Emacs 20.7.1
From: gson@nominum.com (Andreas Gustafsson)
Sender: owner-ietf@ietf.org
Precedence: bulk

On the IETF list, Claus Färber wrote:
> I think the only requirement that's really essential is that the serial
> number changes whenever the data that would be returned by a zone
> transfer changes (even if that breaks database consistency for the SOA
> record's serial number).

It is also essential that two different authoritative servers that
show the same serial number actually serve the same data.

> One strategy to implement this would be to keep an exact copy of a zone
> obtained from other servers for outgoing transfers (so you'll always use
> the original serial number), which is the BIND 9 strategy.
> 
> Another strategy would be to just increment the serial number of a zone
> when it is actually changed by importing glue records from another zone.
> This would solve the synchronisation problem, too: If the parent zone is
> updated too early, the server might throw away the glue record. But it
> will update the parent zone and increase its the serial number when it
> gets an up-to-date copy of the child zone.

In principle, this approach could work on the primary master server
(at least assuming the zone serial number is being maintained by the
server rather than the administrator), but it won't work on a slave.

If a slave "imports" glue into a zone, it can't update the serial
number, and even if it could, that wouldn't make the zone contents
consistent with the master.

Followups to namedroppers, please.
-- 
Andreas Gustafsson, gson@nominum.com



From owner-ietf@ietf.org  Fri Feb 28 19:37:26 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18405;
	Fri, 28 Feb 2003 19:37:26 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ov46-0008Ks-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 19:41:22 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ov3H-0008Jr-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 19:40:31 -0500
Received: from maude.qualcomm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18250
	for <ietf@ietf.org>; Fri, 28 Feb 2003 19:31:42 -0500 (EST)
Received: from karn by maude.qualcomm.com with local (Exim 3.35 #1 (Debian))
	id 18ouwf-00026N-00; Fri, 28 Feb 2003 16:33:41 -0800
From: ietf1@ka9q.net
To: phoffman@imc.org
Cc: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
Reply-to: karn@qualcomm.com
Message-Id: <E18ouwf-00026N-00@maude.qualcomm.com>
Date: Fri, 28 Feb 2003 16:33:41 -0800
Sender: owner-ietf@ietf.org
Precedence: bulk

>Could you elaborate a bit on what you mean by "meaningful"? As someone
>who uses the DUL list as an anti-spam mechanism and who experiments
>with turning it off and on, I can definitely say that turning it on
>reduces the amount of spam I receive (on the order of about 100
>messages a day).

Certainly. Here's another good spam-blocking strategy:

Turn off your SMTP listener.

Although highly effective at stopping spam, this method is not
meaningful.

Perhaps I should have used a better word, such as "selective", to
imply methods that are much more likely to stop spam than
non-spam. The MAPS DUL does not discriminate between spam or non-spam,
or even between users who have generated spam in the past and those
that do not. If you're a dialup user, you are automatically guilty of
spamming even if you can prove yourself innocent.

>I recognize that it also harms folks like you for many of the reasons
>you give. But I don't understand why you say it is not a meaningful
>anti-spam mechanism.

Here's another way that the MAPS DUL is not meaningful. Comcast, which
just put all their cable modem IP address blocks in the MAPS DUL, says
that if you upgrade to one of their expensive commercial services you
can get a block of static IP addresses instead of one dynamic
address. And those static addresses will not be placed on the MAPS
DUL.

So if all you have to do to evade a supposed anti-spam mechanism is to
pay some more money to your ISP, do you still consider that mechanism
to be "meaningful"? Or is it just a way for your ISP to cynically
profit from spam with a mechanism they claim to be anti-spam?

Phil





From owner-ietf@ietf.org  Fri Feb 28 19:46:35 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18664;
	Fri, 28 Feb 2003 19:46:35 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ovCo-0000Pt-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 19:50:22 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ovC9-0000Oo-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 19:49:41 -0500
Received: from stoneport.math.uic.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA18568
	for <ietf@ietf.org>; Fri, 28 Feb 2003 19:40:53 -0500 (EST)
Received: (qmail 37444 invoked by uid 1016); 1 Mar 2003 00:43:19 -0000
Date: 1 Mar 2003 00:43:19 -0000
Message-ID: <20030301004319.37443.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org, ietf@ietf.org
Subject: Re: Poison in a zone
References: <20030225005042.72047.qmail@cr.yp.to> <8giJ0Pz3cDD@3247.org> <200303010006.h2106Zm21440@guava.araneus.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf@ietf.org
Precedence: bulk

Andreas Gustafsson writes:
> It is also essential that two different authoritative servers that
> show the same serial number actually serve the same data.

That's a wild exaggeration. For example, a pure slave can do anything it
wants with its serial numbers. In fact, unless one slave pulls the zone
from two different masters, serial-number coherency is irrelevant.

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



From owner-ietf@ietf.org  Fri Feb 28 20:09:16 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19167;
	Fri, 28 Feb 2003 20:09:16 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18ovZ4-0001GM-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 20:13:22 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ovZ2-0001FI-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 20:13:20 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19133
	for <ietf@ietf.org>; Fri, 28 Feb 2003 20:04:30 -0500 (EST)
Received: by as.vix.com (Postfix, from userid 716)
	id B1404379EF5; Sat,  1 Mar 2003 01:06:29 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
References: <E18ouwf-00026N-00@maude.qualcomm.com>
From: Paul Vixie <vixie@vix.com>
Date: 01 Mar 2003 01:06:29 +0000
In-Reply-To: <E18ouwf-00026N-00@maude.qualcomm.com>
Message-ID: <g3of4vdhey.fsf@as.vix.com>
Lines: 44
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf@ietf.org
Precedence: bulk

phil wrote:

> Perhaps I should have used a better word, such as "selective", to
> imply methods that are much more likely to stop spam than
> non-spam. The MAPS DUL does not discriminate between spam or non-spam,
> or even between users who have generated spam in the past and those
> that do not. If you're a dialup user, you are automatically guilty of
> spamming even if you can prove yourself innocent.

you had me until the final sentence.  the maps dul is a list of dialups,
not a list of guilty spammers.  anyone who subscribes to it knows what they
are getting.  (i no longer speak for maps, but i know what the dul is.)

> Here's another way that the MAPS DUL is not meaningful. Comcast, which
> just put all their cable modem IP address blocks in the MAPS DUL, says
> that if you upgrade to one of their expensive commercial services you
> can get a block of static IP addresses instead of one dynamic
> address. And those static addresses will not be placed on the MAPS DUL.

if comcast would ask maps to list things on the dul which were not dialups,
then there could be a problem.  but since the dul is just a list of dialups,
it seems very meaningful that comcast asks maps to put their dialups on it.

> So if all you have to do to evade a supposed anti-spam mechanism is to
> pay some more money to your ISP, do you still consider that mechanism
> to be "meaningful"? Or is it just a way for your ISP to cynically
> profit from spam with a mechanism they claim to be anti-spam?

a long time ago i warned that the real victim of spam would be "openness"
and that when closed communities with gates started appearing, then we would
all know that we had lost the battle.  what i failed to predict was how long
the "losing" would last before "lost" was generally considered obvious.

it seems that comcast has determined that it costs them a lot more support
expense for a customer who can initiate SMTP than for a customer who can't.
they may also have discovered that such customers are willing to pay more.
and they have certainly discovered that maps's dul is a voluntary method
by which they can reduce or limit their support expenses on customers who
are not paying extra for the "initiate SMTP" service.

if you don't believe that comcast ought to have the ability to control how
its services are used, then your recourse is the local PUC, and the FCC.

paul



From owner-ietf@ietf.org  Fri Feb 28 21:59:08 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20957;
	Fri, 28 Feb 2003 21:59:08 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oxAj-0003jK-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 21:56:21 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18ox8i-0003gM-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 21:54:16 -0500
Received: from conure.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20742
	for <ietf@ietf.org>; Fri, 28 Feb 2003 21:45:25 -0500 (EST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18ox23-0004L8-00; Fri, 28 Feb 2003 18:47:24 -0800
Date: Fri, 28 Feb 2003 21:44:16 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Paul Vixie <vixie@vix.com>
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
Message-Id: <20030228214416.460e983c.moore@cs.utk.edu>
In-Reply-To: <g3of4vdhey.fsf@as.vix.com>
References: <E18ouwf-00026N-00@maude.qualcomm.com>
	<g3of4vdhey.fsf@as.vix.com>
X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf@ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> the maps dul is a list of dialups,
> not a list of guilty spammers.  anyone who subscribes to it knows what they
> are getting. 

yes, but are they being misled into thinking it's a good idea to block smtp
traffic just because it comes from a dialup line?



From owner-ietf@ietf.org  Fri Feb 28 22:43:14 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21435;
	Fri, 28 Feb 2003 22:43:14 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oxvD-0005AS-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 22:44:23 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oxv0-00058z-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 22:44:10 -0500
Received: from as.vix.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21348
	for <ietf@ietf.org>; Fri, 28 Feb 2003 22:35:21 -0500 (EST)
Received: from as.vix.com (localhost [127.0.0.1])
	by as.vix.com (Postfix) with ESMTP id 9A28D379EF8
	for <ietf@ietf.org>; Sat,  1 Mar 2003 03:37:18 +0000 (GMT)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms? 
In-Reply-To: Message from Keith Moore <moore@cs.utk.edu> 
	of "Fri, 28 Feb 2003 21:44:16 EST."
	<20030228214416.460e983c.moore@cs.utk.edu> 
X-Mailer: MH-E 7.2; nmh 1.0.4; GNU Emacs 21.2.1
Date: Sat, 01 Mar 2003 03:37:18 +0000
Message-Id: <20030301033718.9A28D379EF8@as.vix.com>
Sender: owner-ietf@ietf.org
Precedence: bulk

> > the maps dul is a list of dialups, not a list of guilty spammers.
> > anyone who subscribes to it knows what they are getting.
> 
> yes, but are they being misled into thinking it's a good idea to block
> smtp traffic just because it comes from a dialup line?

to keep that question from fitting the definition of "FUD", i suggest
that you treat it as real (nonrhetorical) and try to find the answer.



From owner-ietf@ietf.org  Fri Feb 28 23:34:22 2003
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22045;
	Fri, 28 Feb 2003 23:34:21 -0500 (EST)
Received: from majordomo by ran.ietf.org with local (Exim 4.10)
	id 18oyhd-0006Y1-00
	for ietf-list@ran.ietf.org; Fri, 28 Feb 2003 23:34:25 -0500
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org)
	by ran.ietf.org with esmtp (Exim 4.10)
	id 18oygh-0006WT-00
	for ietf@ran.ietf.org; Fri, 28 Feb 2003 23:33:27 -0500
Received: from calcite.rhyolite.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21955
	for <ietf@ietf.org>; Fri, 28 Feb 2003 23:24:36 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.7.Beta0/8.12.7.Beta0) id h214QTrG005393
	for ietf@ietf.org env-from <vjs>;
	Fri, 28 Feb 2003 21:26:29 -0700 (MST)
Date: Fri, 28 Feb 2003 21:26:29 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200303010426.h214QTrG005393@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IAB policy on anti-spam mechanisms?
References: <20030228214416.460e983c.moore@cs.utk.edu>
Sender: owner-ietf@ietf.org
Precedence: bulk

> From: Keith Moore <moore@cs.utk.edu>
> To: Paul Vixie <vixie@vix.com>

> > the maps dul is a list of dialups,
> > not a list of guilty spammers.  anyone who subscribes to it knows what they
> > are getting. 

That's both wrong and misleading.  

It is misleading because the essentially none of people whose incoming
mail is affected by the DUL, PDL, RBL+, SpamAassassin, Brightmail, Postini,
DCC, and every other even slightly popular spam filter do any "subscribing."
except to their ISP.  There are only 10,000s of people who can be said
to "subscribe" to any spam filtering, and they subscribe on behalf of
probably more than 100,000,000 mailboxes.  Those 100M users do not
"subscribe" to anything except mysterious services provided by their ISP.
They would not understand the implications of the filtering their ISPs
provide if they were told.  The most users are told is a brand name, some
technobabble, and perhaps how to add to personal white- or blacklists.

Paul's statement is wrong in that most of the relatively very few
people who do "subcribe" to Brightmail, Postini, the DUL, PDL, RBL+,
Pyzor, SpamAassassin, and even the DCC do not understand what they're
subscribing to.  Perhaps Paul's experience some time ago when he was
involved with MAPS differs from what I've found with the thousands of
installations of the DCC.  I try hard to disclose everything to everyone
about the DCC except details of the fuzzy checksums, but much less
than 10% get it or care.

I don't want to insult anyone, but subscribers treat spam filters like
the other black boxes they deal with.  They don't care how a filter
works if it has less than 10%-15% false negatives and less than 1%
false positives.  They care even less about worse filters.  They may
pick up some technobabble, but they use it like they used to talk
about routers ASICs without any real notion of how the differences
among ASICs, full-custom silicon, and commodity MPUs might matter.

I doubt many of the few people who do "subscribe" to the DUL on behalf
of their users understand it.  From comments in other forums it is
clear that many do not realize that or why many "dialup" blacklists
including many IP addresses that have nothing to do with modems, unless
you think DSLAMs and DOCSIS involve "dialup modems."


> yes, but are they being misled into thinking it's a good idea to block smtp
> traffic just because it comes from a dialup line?

How can they by misled into thinking something they don't understand
and that isn't strictly true?  I'm not sure about the DUL, but the PDL
says it includes a lot more than the classic definition of "dialup line."
(See http://www.pan-am.ca/pdl/ )

However, the truth in that statement means that a statement by the
IETF would be a good thing, no matter what you think of redirection
proxies, port 25 filtering, and "dialup" DNS blacklists.



> From: Paul Vixie <paul@vix.com>

> > yes, but are they being misled into thinking it's a good idea to block
> > smtp traffic just because it comes from a dialup line?
>
> to keep that question from fitting the definition of "FUD", i suggest
> that you treat it as real (nonrhetorical) and try to find the answer.

"Dialup blacklists" no longer have the utility they once did, but have
a new power.  If you understand and believe in dialup blacklists, it's
not because you care about dialup modems.  Most spammers don't use
throw-away modem accounts as they once did.  Instead they abuse open
proxies on DSL and cable-modem networks.  The IP address of those
proxes are often listed in "dialup" blacklists.

However, I see practically no little spam that is not caught by
mechanisms other than "dialup" blacklists.


Vernon Schryver    vjs@rhyolite.com

Disclaimer/advertisement:  http://www.dcc-servers.net/



