Hi,
Thanks for posting the adopted draft.
I think we need to make the following changes so catch all of the IANA
issues associated with being Experimental.
Cheers,
Adrian
===
New section...
6.2. Experimental Error-Types and Error-Values
This experiment uses a single Experimental Use error-type
[I-D.farrel-pce-experimental-errors] to indicate 'PCEP-LS Error' to
cover all experimental error cases. The value used needs to be
consistent between all partners in the experiment, and
implementations would ideally make it configurable.
The following error-values apply to this experimental error-type.
Error-Value | Meaning
+
1 | LS Synchronisation Error: Error in processing the LSRpt
2 | LS Synchronisation Error: Internal PCC error
3 | Mandatory object missing: LS object missing
4 | Invalid Operation: Attempted LS Report if LS remote
| capability was not advertised
---
New section...
6.3. Experimental PCEP TLV Types
This document uses a number of experimental PCEP TLVs. Values are
chosen from the Experimental Use range. The values used need to be
consistent between all partners in the experiment, and
implementations would ideally make them configurable.
For clarity in the document, the TLVs are indicated using the tags
EXPx for different values of x, as follows.
Value | Meaning
---+
EXP5 | LS-CAPABILITY TLV
EXP7 | ROUTING-UNIVERSE TLV
EXP8 | Local Node Descriptors TLV
EXP9 | Remote Node Descriptors TLV
EXP10 | Link Descriptors TLV
EXP11 | Prefix Descriptors TLV
EXP12 | Node Attributes TLV
EXP13 | Link Attributes TLV
EXP14 | Prefix Attributes TLV
EXP15 | ROUTE-DISTINGUISHER TLV
---
Throughout the document, make the following changes
TBD5 --> EXP5
TBD7 --> EXP7
TBD8 --> EXP8
TBD9 --> EXP9
TBD10 --> EXP10
TBD11 --> EXP11
TBD12 --> EXP12
TBD13 --> EXP13
TBD14 --> EXP14
TBD15 --> EXP15
---
6.2
OLD
The LS reports sent by PCC MAY carry the remote link-state (and TE)
information learned via existing means like IGP and BGP-LS only if
both PCEP Speakers set the R (remote) Flag in the "LS Capability" TLV
to 'Remote Allowed (R Flag = 1)'. If this is not the case and LS
reports carry remote link-state (and TE) information, then a PCErr
with error-type 19 (Invalid Operation) and error-value TBD1
(Attempted LS Report if LS remote capability was not advertised) and
it will terminate the PCEP session.
NEW
The LS reports sent by PCC MAY carry the remote link-state (and TE)
information learned via existing means like IGP and BGP-LS only if
both PCEP Speakers set the R (remote) Flag in the "LS Capability" TLV
to 'Remote Allowed (R Flag = 1)'. If this is not the case and LS
reports carry remote link-state (and TE) information, then a PCErr
with the experimental error-type (PCEP-LS Error) and error-value
(Attempted LS Report if LS remote capability was not advertised) and
it will terminate the PCEP session.
END
---
6.3
OLD
If the PCC encounters a problem which prevents it from completing the
LS synchronization, it MUST send a PCErr message with error-type TBD2
(LS Synchronization Error) and error-value 2 (indicating an internal
PCC error) to the PCE and terminate the session.
NEW
If the PCC encounters a problem which prevents it from completing the
LS synchronization, it MUST send a PCErr message with the
experimental error-type (PCEP-LS Error) and error-value 2 (LS
Synchronization Error: Internal PCC error) to the PCE and terminate
the session.
END
---
6.3
OLD
The PCE does not send positive acknowledgments for properly received
LS synchronization messages. It MUST respond with a PCErr message
with error-type TBD2 (LS Synchronization Error) and error-value 1
(indicating an error in processing the LSRpt) if it encounters a
problem with the LS Report it received from the PCC and it MUST
terminate the session.
NEW
The PCE does not send positive acknowledgments for properly received
LS synchronization messages. It MUST respond with a PCErr message
with with the experimental error-type (PCEP-LS Error) and error-value
1 (LS Synchronization Error: Error in processing the LSRpt) if it
encounters a problem with the LS Report it received from the PCC and
it MUST terminate the session.
END
---
8.1
OLD
The Message-Type field of the PCEP common header for the
LSRpt message is set to [TBD3].
NEW
The Message-Type field of the PCEP common header for the
LSRpt message is set to a value from the range of Experimental Use
message types. The value used needs to be consistent between all
partners in
