Should the baggage propagator clear pre-existing baggage?

[MrAlias]

Based on the 1.0.1 version of the Baggage specification:

If the propagator is unable to parse the incoming baggage, extract MUST return a Context with no baggage entries in it.
If the incoming baggage is present, but contains no entries, extract MUST return a Context with no baggage entries in it.

The TextMap Extract specification states that the extract method is passed a context and returns a derived context.

Based on the existing specification if a context contains valid Baggage values and is passed to the baggage propagator to extract an unparssable or empty baggage into those existing values will be cleared. Is this intended?

[MrAlias]

From the specification SIG meeting the take-away is that if an extraction fails it needs to not touch what is in the existing context. This is specified here:

If a value can not be parsed from the carrier, for a cross-cutting concern, the implementation MUST NOT throw an exception and MUST NOT store a new value in the Context, in order to preserve any previously existing valid value.

I'm going to open a PR to correct this language.