[sidr] sidr - New Meeting Session Request for IETF 97

["IETF Meeting Session Request Tool"]

A new meeting session request has just been submitted by Sandra L. Murphy, a 
Chair of the sidr working group.


-
Working Group Name: Secure Inter-Domain Routing
Area Name: Routing Area
Session Requester: Sandra Murphy

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 90
Conflicts to Avoid: 
 First Priority: opsec idr grow saag rtgwg rtgarea
 Second Priority: dane i2rs isis trill lamps



Special Requests:
  
-

___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] adverse actions -01 posted

[Christopher Morrow]

On Tue, Aug 2, 2016 at 3:54 PM, Stephen Kent  wrote:

> Randy
>
>> Tim offered no suggestion for a different term, which is not helpful.
>
 the suggestion was "unwanted".

>>> I reread Tim's message; I don't interpret it as having suggested
>>> "unwanted" as an alternative.
>>>
>> that is clear.  others, such as matthias and i, did.  but this is not
>> productive.
>>
>> to be clear, i hereby suggest s/adverse/unwanted/
>>
> I will process your suggestion in the same spirit that you continue to
> ignore my comments about revising the folksy language in the LTA use cases
> document.
>
> The term "adverse" is appropriate here.
>
>
The discussion here seems to be about (though I haven't seen this word
used) connotations attached to 'adverse'.  'by the english definition'
 adverse may be correct. It may be worth using 'unwanted' though to avoid
the connotations associated with 'adverse' ?

Is the point here that occasionally a parent my ask you to eat your peas,
while you don't enjoy that thought?


> Contrary to Tim's assertion, it does not imply, ".. that for conscious
> actions by a parent CA against the will by a child CA, the parent is
> "wrong" and the child is "right."
>
> "unwanted" is a wimpy term that fails to convey the fact that the actions
> have a negative impact on the INR holder.
>
> Steve
>
>
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

[sidr] Current document status && directionz

[Chris Morrow]

Howdy SIDR peeps,
(+bonus ops ad)

Following on the Berlin meeting we were trying to accomplish two
things:

  1) get all documents related to sidr protocols into wglc and then
  publication

  2) get all documents which are more operationally focused moved
  along to an ops group (sidr-ops or something akin to that)

With that in mind there are 8 documents in the publication queue:
  draft-ietf-sidr-as-migration
  draft-ietf-sidr-bgpsec-algs
  draft-ietf-sidr-bgpsec-ops
  draft-ietf-sidr-bgpsec-overview
  draft-ietf-sidr-bgpsec-pki-profiles
  draft-ietf-sidr-bgpsec-protocol
  draft-ietf-sidr-origin-validation-signaling
  draft-ietf-sidr-rpki-rtr-rfc6810-bis

and 11 still in progress. Of the 11 left Sandy and I think they
roughly break down like:

Documents which should move to the ops group:
  draft-ietf-sidr-bgpsec-rollover
  draft-ietf-sidr-lta-use-cases
  draft-ietf-sidr-route-server-rpki-light - authors notified/queried about this
  draft-ietf-sidr-rtr-keying

documents which should finish out in sidr:
  draft-ietf-sidr-delta-protocol
  draft-ietf-sidr-publication
  draft-ietf-sidr-rpki-oob-setup - pub request in flight
  draft-ietf-sidr-rpki-tree-validation
  draft-ietf-sidr-rpki-validation-reconsidered
  draft-ietf-sidr-slurm - authors recently updated
  draft-ietf-sidr-adverse-actions - wglc imminent

I think if there's no meaningful discussion on change for these
between now and 9/16/2016 (Sept 16th) we will assume this list is
correct. For documents in the 'move' list, if progress to publication
happens 'good!'. For all documents in the 'stays' list:
  1) we aim to have wglc by Seoul
  2) publication requests started on as many as possible

We plan to meet in Seoul, but not in Chicago (Mar 2017) where we
expect the ops group to exist and meet. We can progress documents in
SIDR after Seoul, but the WG should close out shortly after the new
year. (or that's the goal).

Thoughts?
-chris

___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr