Re: Checksum at IP layer - is it even needed ?

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 17 December 2015 09:49 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22541A874E for <ietf@ietfa.amsl.com>; Thu, 17 Dec 2015 01:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.899
X-Spam-Level:
X-Spam-Status: No, score=0.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mTpkxoPlH7T6 for <ietf@ietfa.amsl.com>; Thu, 17 Dec 2015 01:49:19 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 472D61A8737 for <ietf@ietf.org>; Thu, 17 Dec 2015 01:49:19 -0800 (PST)
Received: (qmail 76263 invoked from network); 17 Dec 2015 09:30:52 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 17 Dec 2015 09:30:52 -0000
Subject: Re: Checksum at IP layer - is it even needed ?
To: Patrik Fältström <paf@frobbit.se>
References: <CAOJ6w=Eu9PP1-xhk+pKWfi0dS2x2WsxdNeg-Puywx0cZZ1Gw=A@mail.gmail.com> <CAAeewD-A7-Ea3aia+_b7QrZLxABiUigRudcL9og1kkmb5L6gpQ@mail.gmail.com> <BE5A47FB-EE37-4692-9BB3-890BEA0A0FAC@puck.nether.net> <CAOJ6w=EZV+kr54Yy_OojoTKGW0X_v8nDUngbZYx6H2s_gV64wg@mail.gmail.com> <E1737903-5251-430A-AE3B-D65673865797@puck.nether.net> <566FD181.4030403@necom830.hpcl.titech.ac.jp> <20151215130035.GA5511@puck.nether.net> <56710AFE.8000004@necom830.hpcl.titech.ac.jp> <CAAeewD8ZOfYZOhjf-B_G6qCiMkrdwsWXzyF2FYy_WDSfPKgS_g@mail.gmail.com> <5671607E.5090809@necom830.hpcl.titech.ac.jp> <B0A81AEF-C5F3-46B4-94B0-B06B28ACA765@frobbit.se> <56726064.9030200@necom830.hpcl.titech.ac.jp> <306DA5BA-D4AC-4797-A559-D18F27C12B6F@frobbit.se>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <56728517.8060204@necom830.hpcl.titech.ac.jp>
Date: Thu, 17 Dec 2015 18:49:11 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <306DA5BA-D4AC-4797-A559-D18F27C12B6F@frobbit.se>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hkRlMGXvxtsLgiB38BX1bu5VxXM>
Cc: ietf <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Dec 2015 09:49:20 -0000

Patrik Fältström wrote:

>> URI RR can not be used by applications without URL specifications,
>> whereas SRV can be used by any applications using hostnames (and
>> having IANA registered (or, well known?) service name).
>
> If you as an application query for a specific service, you should be prepared
 > to receive all URI schemes that can be used for that service.

What if there is no URL scheme that can be used for that service?

As Jared Mauch wrote:

 >> And it can be automated if browsers support SRV, a DNS RR type to
 >> specify non-default port numbers.
 >
 > 	I'm not talking about a browser.

don't assume all the applications are living in HTTP world and have
URLs to describe the applications.

> I.e. if you query for _http._tcp.example.com. it would be confusing
 > and weird if you get a SIP-URI scheme back.

Suppose that there is no http scheme defined, in which case, no
URL could be returned from the beginning.

For example, what URL could be placed at "_domain._tcp.example.com"?

						Masataka Ohta