First, sorry for any duplicates, but we wanted to reach all
After several discussions with many different folks last week
at IETF 67 in San Diego, as well as various people over the
course of the past few months, Dan Senie and I have decided to
undertake an effort to "update" RFC2827/BCP38 .
I know that I'm not the only person who has heard various
discussions in the past couple of years that concluded that
(paraphrased), "BCP38 needs to be updated."
Now is your chance to speak up.
We would very much like to solicit comments & suggestions from the
community-at-large on areas where you feel BCP38 is lacking, or in
areas where you feel it does not properly address with regards to
prohibiting source-spoofed traffic from any given administrative
network boundary, given that some technical aspects of the Internet
may have changed since it's publication.
While we acknowledge that a uniform application of a source address
verification architecture/ingress filtering scheme will not mitigate
_all_ "unwanted traffic"  in the Internet, it will most certainly
address the issue of hosts which attempt to source-spoof traffic into
I have not set up a mailing list for this yet, but if there is
enough discussion/input, I will make an effort to do so (or perhaps
the SAVA mailing list  might be a good place for discussion). In
the interim, you can contact me or Dan directly:
fergie & dan
p.s. Also, for anyone who might be interesting in related work,
there is an effort to bring some additional work into the IETF
called SAVA, or Source Address Validation Architecture .