Terry Manderson has entered the following ballot position for
draft-ietf-sidr-as-migration-05: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Hi,
I support working group adoption,
Oliver
On 5/3/16, 5:55 AM, "sidr on behalf of Tim Bruijnzeels" wrote:
>Hi,
>
>I believe this is useful work and support adoption. Happy to contribute to the
>discussion where I can.
>
>Tim
>
>
>
>
>>
+1 to Roque's point. Definitely standards track.
Thanks,
Sharon
On Tue, Apr 19, 2016 at 6:31 PM, Roque Gagliano (rogaglia) <
rogag...@cisco.com> wrote:
> +1 with Standard Track.
>
> The question could have been relevant six years ago and we may not have
> debated it that much then. Today, we
howdy, it's past 4/29/2016 || 29/4/2016 || Mar 29 2016... and from the
discussion on-list and mostly in the room in EZE, it appears:
"Please maintain Proposed Standard as the track for SIDR work."
i think this closes out the discussion.
thanks for deliberating and discussing this topic!
Hiya,
On 03/05/16 15:02, George, Wes wrote:
> Completing approval on this one while it's in queue
> also seems a better use of IESG cycles
It's a minor point but evaluating this one really calls
for having reviewed bgpsec as well so I think doing this
one 1st will be a slightly less good use of
On 5/3/16, 6:30 AM, "Stephen Farrell" wrote:
>
>Hi Wes,
>
>This is only a timing problem if bgpsec doesn't change in some
>incompatible manner. If such a change happens then this is more
>than a timing issue.
>What'd be bad about just holding this in the WG until
Hi Wes,
(FWIW, I agree with Kathleen's DISCUSS on this but one question
below before I post my own ballot...)
On 02/05/16 20:31, George, Wes wrote:
>
> On 5/2/16, 1:04 PM, "Kathleen Moriarty"
> wrote:
>
>
>>
>>
Hi,
I believe this is useful work and support adoption. Happy to contribute to the
discussion where I can.
Tim
> On 02 May 2016, at 15:32, Carlos M. Martinez wrote:
>
> Hello all,
>
> LACNIC has worked on three projects involving RPKI-enabling IXPs [0]. We
>