IETF Logo Mail Archive

Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 13 January 2013 16:02 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBC021F87A6 for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level:
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7liXCaAu4Erl for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3492321F87A4 for <ietf@ietf.org>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so2915737vbb.3 for <ietf@ietf.org>; Sun, 13 Jan 2013 08:02:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q7NxfqG7fsymNXqVqRtUWQikN6ufy9E4q0PSiFVPGis=; b=nqnsNJl9Fb4JO5uBr6WKskI0o5kK9edV0jMQqPNcfScSLATo9vkebE4OvgVT5t1lE0 UQklMIt6A1XBONVUtemFp0ZO5G1NEP07Tmyab0By9D2PLWsSYGh6Vl9dI6G4MOwiemL8 U2UbtvutfyXXhXOWjITRQ3Y+Eq9unpDOIflTKdlgUP/m9hYqLQJzxmg49AbZV9NqNV5u hOhYvyafJy7QoZzhbJWjRI31Yvs1NBSRRIhy4EIBNoonH78byONjqYgSK32uYn/hmJUQ 7Ba/hbU4vfJ+t+gJUbn3z4IRwkmdRSQQi0/NFBDkEn6sNBPS/rasJjNCf1O8uAeDb4hz EqsA==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr87698890vde.55.1358092932010; Sun, 13 Jan 2013 08:02:12 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 13 Jan 2013 08:02:11 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130112064815.05ffc568@resistor.net>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6.2.5.6.2.20130112064815.05ffc568@resistor.net>
Date: Sun, 13 Jan 2013 17:02:11 +0100
Message-ID: <CADnDZ88Jb6eV1CBmpztVzpw57=gnXhoEq=AqQTNGSjtug=hr_A@mail.gmail.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: arturo.servin@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 16:02:18 -0000

agree with Servin, to update 2050,

AB
+++

On Sun, 13 Jan 2013 12:22:21, Arturo Servin wrote:

I agree that RFC2050 is not completely valid with the current state of
the Internet, but making it historic will not solve any problem IMHO.

Before making 2050 historic, we should think what is and what is not
valid according with today's internet, what the technical community
needs to recommend to the RIR community and make a new document that
updates and obsoletes 2050.

Cheers,
as

v2.23.0 | Report a Bug | By Email