IETF Logo Mail Archive

Re: [babel] [netmod] NULL value for ip-address

Qin Wu <bill.wu@huawei.com> Sat, 18 September 2021 02:10 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8983A20C5; Fri, 17 Sep 2021 19:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 sVs-Ekgx8QNK; Fri, 17 Sep 2021 19:10:53 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA7FF3A20C2; Fri, 17 Sep 2021 19:10:52 -0700 (PDT)
Received: from fraeml713-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HBDkl1PbZz67gjx; Sat, 18 Sep 2021 10:08:31 +0800 (CST)
Received: from dggeml754-chm.china.huawei.com (10.1.199.153) by fraeml713-chm.china.huawei.com (10.206.15.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.8; Sat, 18 Sep 2021 04:10:49 +0200
Received: from dggeml753-chm.china.huawei.com (10.1.199.152) by dggeml754-chm.china.huawei.com (10.1.199.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Sat, 18 Sep 2021 10:10:47 +0800
Received: from dggeml753-chm.china.huawei.com ([10.1.199.152]) by dggeml753-chm.china.huawei.com ([10.1.199.152]) with mapi id 15.01.2308.008; Sat, 18 Sep 2021 10:10:47 +0800
From: Qin Wu <bill.wu@huawei.com>
To: tom petch <ietfc@btconnect.com>
CC: 'Babel at IETF' <babel@ietf.org>, "'netmod@ietf.org'" <netmod@ietf.org>
Thread-Topic: [netmod] [babel] NULL value for ip-address
Thread-Index: AdesMZlN3Gm4X5rLSrqRYOuMUOaqNA==
Date: Sat, 18 Sep 2021 02:10:47 +0000
Message-ID: <59275ad2ed024760b5acc0414ed6e210@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.123.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/cw98oR6rIWd2HQ4D76fRs6oKs8E>
Subject: Re: [babel] [netmod] NULL value for ip-address
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Sep 2021 02:10:55 -0000

Second, left field. when I first posted, I had great difficulty in specifying the e-mail addresses I was sending to (still do:-(.  I included the document shepherd, and you because I knew what your address is and it is easy to type correctly:-)  The addresses I might have included, but did not,  were your fellow author (who is now on the thread); and the WG Chairs, the address for the I-D and perhaps the AD.  I trust that these others will be involved when needed.

Tom Petch

[Qin] I assume you will get bounced with "Too Many Recipients error". The work around is to split recipient into several group and send email message multiple times to each group.
Or you reach a limit for sending email, this case is very rare. 
Or your email client application refuses to work for some recipient's email with specific ASCII character. I met this before. But again this is corner case.

v2.23.0 | Report a Bug | By Email