Dear Author,
I am further expanding my query and raising concern over your
response. The Problem Nos. are same as in the trailing reply.:
Problem 1:
Response: " We assume that in a managed network that the JRC *can* know all the
legitimate manufacturers."
May be!! But practica
Brian E Carpenter wrote:
>> problem 1.
Anoop> The major problem with the procedure is that the registrar doesn’t
Anoop> verify the manufacturer.
>>
>> To translate, the JRC has no obvious way to verify that the "MI" key
belongs
>> to the manufacturer that they care about
On 19/02/2018 21:52, Anoop Kumar Pandey wrote:
> Dear Author,
>
>I am further expanding my query and raising concern over your
> response. The Problem Nos. are same as in the trailing reply.:
>
>
>
> Problem 1:
> Response: " We assume that in a managed network that the JRC *can*
Brian E Carpenter wrote:
>> Problem 1:
>> Response: " We assume that in a managed network that the JRC *can*
>> know all the legitimate manufacturers."
>> May be!! But practically may not be possible. Manufacturers keep
>> adding and also getting out of business. Tracking e
On 20/02/2018 08:15, Michael Richardson wrote:
>
> Brian E Carpenter wrote:
> >> problem 1.
> Anoop> The major problem with the procedure is that the registrar doesn’t
> Anoop> verify the manufacturer.
> >>
> >> To translate, the JRC has no obvious way to verify that the "MI"
Nonwithstanding the more detailled explanations you provided for Anoop,
what i wuild think to be helpful to write into the security ection is like this:
Domain trusting pledge/manufacturer:
BRSKI does not fundamentally change this from RFC7030 EST assuming a pledge used
its IDevID with RFC7030 ES
“ANIMA is scoped to support professionally managed networks. So it seems
reasonable to assume that they have procurement procedures in place to buy from
known sources and not to buy kit "off the back of a lorry" to use a British
idiom.”
"Again - a professionally managed network! Our goal in
Anoop,
> So, basically you reduced your scope to a professionally managed network.
The term 'professionally managed' is in the ANIMA charter, see
https://datatracker.ietf.org/doc/charter-ietf-anima/
It was just meant to provide a clear delineation of anima vs. Homenet or
similar networks,
whi
