IETF Logo Mail Archive

[dhcwg] [DHCPv6]Petty question regarding MRC in RFC3315

<Hideshi.Enokihara@jp.yokogawa.com> Fri, 02 February 2007 09:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCv0n-0000E3-FS; Fri, 02 Feb 2007 04:47:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCv0m-0000Dh-2h for dhcwg@ietf.org; Fri, 02 Feb 2007 04:47:16 -0500
Received: from zns001-0m9004.yokogawa.co.jp ([203.174.79.162]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCv0k-0006Ph-HV for dhcwg@ietf.org; Fri, 02 Feb 2007 04:47:16 -0500
Received: from zns001-0m9004.yokogawa.co.jp (localhost [127.0.0.1]) by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id l129l173014381 for <dhcwg@ietf.org>; Fri, 2 Feb 2007 18:47:01 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23]) by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id l129kvAU014349 for <dhcwg@ietf.org>; Fri, 2 Feb 2007 18:47:01 +0900 (JST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Feb 2007 18:46:56 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B898985@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [DHCPv6]Petty question regarding MRC in RFC3315
Thread-Index: AcdGrxOcgloKlnFqQJ6r4e6b+RkK1w==
From: Hideshi.Enokihara@jp.yokogawa.com
To: dhcwg@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [dhcwg] [DHCPv6]Petty question regarding MRC in RFC3315
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi all,

I'd like to know your thought regarding MRC meaning.

RFC3315 section 14 says,
-----------
(snip)
      MRC    Maximum retransmission count  
(snip)
   MRC specifies an upper bound on the number of times a client may
   retransmit a message.  Unless MRC is zero, the message exchange fails
   once the client has transmitted the message MRC times.
---------

Does this mean that MRC is the number of retransmitted messages?
For example, in the case of MRC  is 3 and message type is Solicit,
which behavior is correct?
[Case 1]
Client
	transmit 		1st Solicit 	---->
	retransmit(MRC=1)	2nd Solicit 	---->
	retransmit(MRC=2)	3rd Solict	---->
	retransmit(MRC=3)	4th Solicit	---->
	no more transmit of Solicit

or

[Case 2]
Client
	transmit (MRC=1)	1st Solicit 	---->
	retransmit(MRC=2)	2nd Solicit 	---->
	retransmit(MRC=3)	3rd Solict	---->
	no more transmit of Solicit

Could you let me know which behavior is correct, please?

Best regards,
....Hideshi

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email