Skip to main content

Source Address Validation in Intra-domain and Inter-domain Networks
charter-ietf-savnet-01

Yes

Paul Wouters
Éric Vyncke
(Alvaro Retana)
(Robert Wilton)

No Objection

Erik Kline
Francesca Palombini
Murray Kucherawy
Roman Danyliw
Zaheduzzaman Sarker

Note: This ballot was opened for revision 00-02 and is now closed.

Ballot question: "Do we approve of this charter?"

Paul Wouters
Yes
Éric Vyncke
(was No Objection) Yes
Erik Kline
No Objection
Francesca Palombini
No Objection
Murray Kucherawy
No Objection
Roman Danyliw
No Objection
Zaheduzzaman Sarker
No Objection
Alvaro Retana Former IESG member
Yes
Yes (for -00-03) Not sent

                            
Robert Wilton Former IESG member
Yes
Yes (for -00-03) Not sent

                            
Lars Eggert Former IESG member
No Objection
No Objection (2022-06-16 for -00-03) Sent
# GEN AD review of charter-ietf-savnet-03

CC @larseggert

## Comments

### Paragraph 2
```
  The "Source Address Validation in Intra-domain and Inter-domain Networks
  (SAVNET)" working group will define routing protocol-independent architectures
  and procedures to accurately determine the valid incoming router interfaces for
  specific source prefixes.  The accuracy of the new SAV mechanisms is expected
  to improve upon the current ones.  The WG will not work on extending existing
  mechanisms.
```
Should publication of any new mechanisms be contingent on improving on the current ones?

### "WG", paragraph 0
```
  The scope of the SAVNET WG includes the SAV function for both intra-domain and
  inter-domain networks and the validation of both IPv4 and IPv6 addresses.  The
  WG will address intra-domain solutions first and focus on routing protocol-
  based mechanisms.
```
While the text says the "WG will address intra-domain solutions first", what
does this mean in practice and how will it be enforced? There is nothing gating
work on inter-domain solutions on the completion of the intra-domain ones. The
proposed milestones below only express an aspirational order of work.

### "WG", paragraph 8
```
  After each of the items above has reached WG consensus, a discussion about
  whether it is appropriate to continue must occur.
```
I don't know what is meant by this. When something reaches WG consensus,
shouldn't it be obvious that the WG has decided that the item is appropriate to
continue work on (towards completing it?)

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Typos

#### Paragraph 1
```
- (SAVNET)" working group will define routing protocol-independent architectures
-                                            ^
+ (SAVNET)" working group will define routing-protocol-independent architectures
+                                            ^
```
## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool