Message 196081 - Python tracker
Message196081
| Author | ncoghlan |
|---|---|
| Recipients | christian.heimes, jcea, leim, macfreek, ncoghlan, pmoody, santoso.wijaya, terry.reedy |
| Date | 2013-08-24.15:03:15 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1377356595.85.0.880570551558.issue17400@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Reopening this - rewording the issue title to cover the problem to be solved (i.e. accounting for RFC 6598 addresses) rather than a specific solution (which isn't appropriate, since the RFC *explicitly* states that shared addresses and private addresses aren't the same thing) It seems to me that the simplest solution would be to use the terminology from RFC 6598 and add a new "is_shared" attribute to addresses. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-24 15:03:15 | ncoghlan | set | recipients: + ncoghlan, terry.reedy, jcea, macfreek, christian.heimes, pmoody, santoso.wijaya, leim |
| 2013-08-24 15:03:15 | ncoghlan | set | messageid: <1377356595.85.0.880570551558.issue17400@psf.upfronthosting.co.za> |
| 2013-08-24 15:03:15 | ncoghlan | link | issue17400 messages |
| 2013-08-24 15:03:15 | ncoghlan | create | |