Found 1 record.

Status: Verified (1)

RFC 5460, "DHCPv6 Bulk Leasequery", February 2009

Note: This RFC has been updated by RFC 7653

Errata ID: 3571
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Sunil M Gandhewar
Date Reported: 2013-03-28
Verifier Name: Ted Lemon
Date Verified: 2013-04-03

Section 5.2.1 says:

5.2.1. LEASEQUERY-DATA

The LEASEQUERY-DATA message carries data about a single DHCPv6
client’s leases and/or PD bindings on a single link. The purpose of
the message is to reduce redundant data when there are multiple
bindings to be sent. The LEASEQUERY-DATA message MUST be preceded by
a LEASEQUERY-REPLY message. The LEASEQUERY-REPLY carries the query’s
status, the Leasequery’s Client-ID and Server-ID options, and the
first client’s binding data if the query was successful.

LEASEQUERY-DATA MUST ONLY be sent in response to a successful
LEASEQUERY, and only if more than one client’s data is to be sent.
The LEASEQUERY-DATA message’s transaction-id field MUST match the
transaction-id of the LEASEQUERY request message. The Server-ID,
Client-ID, and OPTION_STATUS_CODE options SHOULD NOT be included:
that data should be constant for any one Bulk Leasequery reply, and
should have been conveyed in the LEASEQUERY-REPLY message.

It should say:

5.2.1. LEASEQUERY-DATA

The LEASEQUERY-DATA message carries data about a single DHCPv6
client’s leases and/or PD bindings on a single link. The purpose of
the message is to reduce redundant data when there are multiple
bindings to be sent. The LEASEQUERY-DATA message MUST be preceded by
a LEASEQUERY-REPLY message. The LEASEQUERY-REPLY carries the query’s
status, the Leasequery’s Client-ID and Server-ID options, and the
first client’s binding data if the query was successful.

LEASEQUERY-DATA MUST ONLY be sent in response to a successful
LEASEQUERY, and only if more than one client’s data is to be sent.
The LEASEQUERY-DATA message’s transaction-id field MUST match the
transaction-id of the LEASEQUERY request message. The Server-ID,
requestor's Client-ID, and OPTION_STATUS_CODE options SHOULD NOT be included:
that data should be constant for any one Bulk Leasequery reply, and
should have been conveyed in the LEASEQUERY-REPLY message.

Notes:

The term "Client-Id" in second paragraph sounds like client's Client-Id and it will be different for more than one client's data. So it should be corrected to "requestor's Client-ID" or "Leasequery's Client-ID" instead of just "Client-ID".

Mark Stapp reviewed this erratum and agrees that it is an improvement. Thanks!

Report New Errata